Download as PDF, PPTX
![CloudStack catch-all datasource
con
fi
guration (/etc/cloud/cloud.cfg)
datasource_list: [ ConfigDrive, CloudStack, None
]
datasource
:
ConfigDrive
:
dsmode: loca
l
CloudStack: {
}
None: {
}
Looks for Con
fi
gDrive
fi
rst, during cloud-init-local,
falls back to checking for virtual router](https://image.slidesharecdn.com/cloud-init-presentation-211011152412/85/CloudStack-and-cloud-init-26-320.jpg)
![Example: setting up data disk
#cloud-confi
g
disk_setup
:
/dev/vdb
:
table_type: gp
t
layout
:
- [33,82
]
- 6
7
fs_setup
:
- label: swa
p
filesystem: swa
p
device: /dev/vdb
1
- label: dat
a
filesystem: ext
4
device: /dev/vdb
2
mounts
:
- [ /dev/vdb1, none, swap, sw, '0', '0'
]
- [ /dev/vdb2, /data, ext4, defaults, '0', '0' ]](https://image.slidesharecdn.com/cloud-init-presentation-211011152412/85/CloudStack-and-cloud-init-28-320.jpg)
More Related Content
Similar to CloudStack and cloud-init
![Cloud init and cloud provisioning [openstack summit vancouver]](https://cdn.slidesharecdn.com/ss_thumbnails/cloud-initandcloudprovisioningopenstacksummitvancouverwip-160517225244-thumbnail.jpg?width=640&height=640&fit=bounds)
CloudStack and cloud-init
- 1.
- 2. What is thiscloud-init? Per the doc: "Cloud-init is the defacto multi-distribution package that handles early initialization of a cloud instance.” A set of services that can be con fi gured to run tasks and set up a VM instance, mostly during the early stages of the VM’s lifecycle A speci fi cation for providing con fi guration to these services. A speci fi cation for adding functionality to these services (modules) Developed by Canonical, dual licensed under GPL3 and Apache 2.0
- 3.
- 4. Boot Stages https://cloudinit.readthedocs.io/en/latest/topics/boot.html 1. Generator- decides if cloud-init services should run 2. Local - cloud-init-local.service - network setup, local datasource 3. Network - cloud-init.service - cloud_init_modules 4. Con fi g - cloud-con fi g.service - cloud_con fi g_modules 5. Final - cloud- fi nal.service - pkg installations, etc
- 5. Datasources https://cloudinit.readthedocs.io/en/latest/topics/datasources.html Cloud-init de fi nes anAPI for fetching userdata and metadata Implement the API to create a datasource CloudStack relevant datasources: CloudStack - Fetched from router VM Con fi gDrive v2 - Fetched from ISO
- 6. Modules https://cloudinit.readthedocs.io/en/latest/topics/modules.html Bundle of codethat implements a speci fi c con fi g task Has a ‘frequency’ property (once, instance, always) Has de fi ned inputs (con fi g keys) accepted via userdata Bundled modules found in cloud-init source at “cloudinit/con fi g” dir Can be referenced to run in “cloud-init”, “cloud-con fi g”, or “cloud- fi nal” stages
- 7.
- 8. Con fi gurations /etc/cloud/cloud.cfg Usually static, templatelevel con fi guration starting point Commonly used to specify which modules and datasources the template supports Userdata con fi guration Dynamic, instance level con fi guration Used to customize Variety of format options Instance metadata Comes from cloud provider, values can be referenced in metadata
- 9. Userdata formats https://cloudinit.readthedocs.io/en/latest/topics/format.html Shell scripts- script is run Include fi le - fi le containing urls to other userdata fi les Upstart job - placed in /etc/init and run as any other Boothook data - stored in /var/lib/cloud and executed Part handler - python, override or provide new module Cloud con fi g - yaml fi le to call modules that perform con fi guration MIME multi-part archive - provide any number of the above, sections labeled with mime tags
- 10. 1. Install cloud-init 2.Con fi gure /etc/cloud/cloud.cfg 3. Create a template 4. Deploy w/userdata
- 11. Installation yum install cloud-init aptinstall cloud-init Kickstart package includes Cloud templates from distributions
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18. /etc/cloud/cloud.cfg (cont’d) /etc/cloud/cloud.cfg overridesa default, built-in cloud.cfg that comes with the distribution package /etc/cloud/cloud.cfg can be overridden by other con fi gs, such as userdata or those provided via CLI when running “cloud-init” manually con fi gs are merged, not replaced Note on overrides
- 19. /etc/cloud/cloud.cfg (cont’d) Add individualmodule to a stage Can override module frequency Modules are run in order of con fi guration Some modules depend on other modules (e.g. runcmd needs scripts-user) De fi ning modules for a stage
- 20. Module con fi guration https://cloudinit.readthedocs.io/en/latest/topics/modules.html “once” -run only once (do not re-run for new instance-id) “once-per-instance” - run on boot when instance-id changes “always” - run every boot Modules have a default frequency, see documentation Module frequency
- 21. Module con fi guration https://cloudinit.readthedocs.io/en/latest/topics/modules.html YAML cloud-con fi gdata Each module has its own supported con fi guration, see documentation Module keys
- 22.
- 23. CloudStack datasources Con fi gured bynetwork offering Virtual router based Con fi gDrive based (cd-rom) Baremetal (MaaS, Canonical)
- 24. Virtual Router Datasource http-based Hostedon virtual router curl http://<router IP>/latest/user-data Router provides data based on caller’s IP Router should also be con fi gured as DHCP server for the network
- 25. Con fi gDrive Datasource ISO imageattached to VM with fi lesystem label “con fi g-2” Con fi gDrive v2 format Can be used for network setup, as it can be processed in the cloud-init- local stage Con fi guration “vm.con fi gdrive.primarypool.enabled” - will host ISO on primary storage when used with KVM
- 26. CloudStack catch-all datasource con fi guration(/etc/cloud/cloud.cfg) datasource_list: [ ConfigDrive, CloudStack, None ] datasource : ConfigDrive : dsmode: loca l CloudStack: { } None: { } Looks for Con fi gDrive fi rst, during cloud-init-local, falls back to checking for virtual router
- 27. Providing user data “deployVirtualmachineuserdata=<base64 encoded>” “updateVirtualmachine userdata=<base64 encoded>” 32kb cloudstack limit with http post Can gzip $ cat my-userdata | gzip | base64 -w0
- 28. Example: setting updata disk #cloud-confi g disk_setup : /dev/vdb : table_type: gp t layout : - [33,82 ] - 6 7 fs_setup : - label: swa p filesystem: swa p device: /dev/vdb 1 - label: dat a filesystem: ext 4 device: /dev/vdb 2 mounts : - [ /dev/vdb1, none, swap, sw, '0', '0' ] - [ /dev/vdb2, /data, ext4, defaults, '0', '0' ]
- 29. Other Examples https://cloudinit.readthedocs.io/en/latest/topics/examples.html Run aptupgrade/yum update Add package repos Set up users, ssh keys, groups, etc. Call a url when fi nished Set up puppet/chef agent Reboot Run arbitrary scripts or write fi les Much more…
- 30. Developing cloud-init data Rememberto clear data, or module frequency con fi g may block execution “cloud-init init” — run the init stage, or the local stage with “—local” fl ag “cloud-init modules” — run init, con fi g, fi nal stages. see “—mode” fl ag “cloud-init clear” — clears data for cloud-init so phases can be run “cloud-init single” — single module, can override frequency with fl ag “cloud-init query” look up value of speci fi c metadata
- 31.
- 32. Semaphores Used to trackthe running of modules and determine frequency thresholds Found in /var/lib/cloud/instance/sem/ and /var/lib/cloud/sem/ Format of semaphore fi les is: <stage>_<module_name>.<frequency> Can be deleted individually to allow re-run of module
- 33.