Finally, I have been able to deploy airsloop on virtual env.
I created two VMs(libvirt/kvm driven), one for genesis and the other for compute node. These two VMs were on the same host. As the compute node VM is supposed to be provisioned by maas via ipmi/pxe. So I used virtualbmc to simulate the ipmi.
I authored the site by following these two guides[1][2]. It’s the mix of guide[1] and guide[2]. The commands I used are all these ones[3].
After fixing several issue, I have deployed the virtual airsloop env. I list here some issues I met:
1. Node identify failed. At the beginning of step ‘prepare_and_deploy_nodes’, the drydock power on the compute node VM via ipmi. Once the compute VM starts up via pxe boot, it runs script to detect local network interfaces and sends the info back to drycok. So the drydock can identify the node based on the received info. But the compute VM doesn’t have real ILO interface, so the drydock can’t identify it. What I did to workaround this was to manually fill the ipmi info on maas web page.
2. My host doesn’t have enough CPU cores, neither the VMs. So I had to increase --pods-per-core in kubelet.yaml.
3. The disk name in compute VM is vda, instead of sda. Drydock can’t map the alias device name to vda, so I had to used the fixed alias name ‘vda’ which is the same as it’s real device name.(it was ‘bootdisk’)
4. My host doesn’t have enough resource(CPU, memory), so I removed some resource consuming components(logging, monitoring). Besides, I disabled the neutron rally test. As it failed with timeout error because of the resource limits.
I also paste my site changes[4] for reference.
[1] https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deploymen... [2] https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html [3] https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-s... [4] https://github.com/cheng1li/treasuremap/commit/7a8287720dacc6dc1921948aaddec...
Thanks, Cheng
From: Anirudh Gupta [mailto:Anirudh.Gupta@hsc.com] Sent: Thursday, May 30, 2019 7:29 PM To: Li, Cheng1 cheng1.li@intel.com; airship-discuss@lists.airshipit.org; airship-announce@lists.airshipit.org; openstack-dev@lists.openstack.org; openstack@lists.openstack.org Subject: RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment
Hi Team,
I am trying to create Airship-Seaworthy from the link https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html
It requires 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes to be configured, but there is no documentation of how to install and getting started with Airship-Seaworthy. Do we need to follow the “Getting Started” section mentioned in Airsloop or will there be any difference in case of Seaworthy. https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-s...
Also what all configurations need to be run from the 3 controller nodes and what needs to be run from 3 computes?
Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता)
From: Li, Cheng1 <cheng1.li@intel.commailto:cheng1.li@intel.com> Sent: 30 May 2019 08:29 To: Anirudh Gupta <Anirudh.Gupta@hsc.commailto:Anirudh.Gupta@hsc.com>; airship-discuss@lists.airshipit.orgmailto:airship-discuss@lists.airshipit.org; airship-announce@lists.airshipit.orgmailto:airship-announce@lists.airshipit.org; openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org; openstack@lists.openstack.orgmailto:openstack@lists.openstack.org Subject: RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment
I have the same question. I haven’t seen any docs which guides how to deploy airsloop/air-seaworthy in virtual env. I am trying to deploy airsloop on libvirt/kvm driven virtual env. Two VMs, one for genesis, the other for compute. Virtualbmc for ipmi simulation. The genesis.sh scripts has been run on genesis node without error. But deploy_site fails at prepare_and_deploy_nodes task(action ‘set_node_boot’ timeout). I am still investigating this issue. It will be great if we have official document for this scenario.
Thanks, Cheng
From: Anirudh Gupta [mailto:Anirudh.Gupta@hsc.com] Sent: Wednesday, May 29, 2019 3:31 PM To: airship-discuss@lists.airshipit.orgmailto:airship-discuss@lists.airshipit.org; airship-announce@lists.airshipit.orgmailto:airship-announce@lists.airshipit.org; openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org; openstack@lists.openstack.orgmailto:openstack@lists.openstack.org Subject: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment
Hi Team,
We want to test Production Ready Airship-Seaworthy in our virtual environment The link followed is
https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.htmlhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fairship-treasuremap.readthedocs.io%2Fen%2Flatest%2Fseaworthy.html&data=02%7C01%7C%7C57c0e7be57a94eb4525908d6e4aad7a3%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C636947819770401915&sdata=DcbHd2umQpPxbk6Lthfh4mlYMCIanqeNcyPPuCITYYk%3D&reserved=0
As per the document we need 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes.
But we need to deploy our setup on Virtual Environment. Does Airship-Seaworthy support Installation on Virtual Environment?
We have 2 Rack Servers with Dual-CPU Intel® Xeon® E5 26xx with 16 cores each and 128 GB RAM. Is it possible that we can create Virtual Machines on them and set up the complete environment.
In that case, what possible infrastructure do we require for setting up the complete setup.
Looking forward for your response.
Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) Hughes Systique Corporation D-23,24 Infocity II, Sector 33, Gurugram, Haryana 122001
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.