![]() In the context of aggregated demand in resource provisioning in the cloud, how does adding n independent demands affect the coefficient of variation (C)?Ģ. NPTEL Cloud Computing Week 3 Assignment Answers 2023ġ. NPTEL Cloud Computing Week 1 Assignment Answers 2023.NPTEL Cloud Computing Week 2 Assignment Answers 2023.NPTEL Cloud Computing Week 3 Assignment Answers 2023.In this exemple I will use the following mapping:īash $ nova aggregate-add-host ephemeral-compute-storage compute01 $ nova aggregate-add-host ephemeral-compute-storage compute02 $ nova aggregate-add-host ceph-compute-storage compute03 $ nova aggregate-add-host ceph-compute-storage compute04Ĭreate a new metadata for this aggregate:īash $ nova aggregate-set-metadata ephemeralcomputestorage=true $ nova aggregate-set-metadata cephcomputestorage=trueīe careful if you modify the name of an aggregate all the metadata will be deleted (behavior seen on Icehouse).Ĭreate a new flavor for the local storage and ceph storage instances:īash $ nova flavor-create m1.ephemeral-compute-stor40 2 $ nova flavor-create m1.ceph-compute-stor40 2Īssign to this flavor a special property:īash $ nova flavor-key m1.ephemeral-compute-storage set ephemeralcomputestorage=true $ nova flavor-key m1. You can use nova hypervisor-list to retrieve hypervisor names like so:īash $ nova hypervisor-list +-+-+ | ID | Hypervisor hostname | +-+-+ | 5 | compute01 | | 2 | compute02 | | 8 | compute03 | | 11 | compute04 | +-+-+ Then create the aggregate that will contain the ceph compute nodes and the local storage compute nodes instances:īash $ nova aggregate-create ephemeral-compute-storage $ nova aggregate-create ceph-compute-storage Live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE,VIR_MIGRATE_PERSIST_DESTįor more details please visit the official Ceph documentation. Ceph storage configuration ¶Įdit your nf and modify: This is the default behavior of Nova so nothing needs to be configured, it is all default. With the help of this filter the nova-scheduler will read virtual machine extra specs: scheduler_default_filters=RetryFilter,AvailabilityZoneFilter,RamFilter,ComputeFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter,AggregateIn In order to instruct Nova that the scheduler has to run through new filters, you must add a new one called AggregateInstanceExtraSpecsFilter to the filters. Thanks agregate filters you will be able to expose these hypervisors. Ultimately, your goal is to dissociate them, fortunately for you OpenStack provides a mechanism based on host agregate that will help you achieve your objective. Virtual machine disks will be highly available so if a compute node crashes you can quickly evacuate the virtual machine disk to another compute node. Then you will be able to seemlessly move virtual machine with the live-migration. On another hand, you want to build hypervisors that where virtual machine root disks will live into Ceph. If the compute node crashes the user will not be able to access his virtual machines for a certain amount of time. Data on the hypervisors will not have a good availability level too. However you will lose handy features like the live-migration (block migration is still an option but slower). Using local storage will help you maximasing your IOs and will reduce IO latentcies to the minimum (compare to network block storage). At some point, you might want to build hypervisor and use their local storage for virtual machine root disks. Computes with Ceph image backend and computes with local image backend.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |