<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:"Lucida Console";
        panose-1:2 11 6 9 4 5 4 2 2 4;}
@font-face
        {font-family:"Nirmala UI";
        panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:1701129720;
        mso-list-type:hybrid;
        mso-list-template-ids:814004160 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D;mso-fareast-language:ZH-CN">Finally, I have been able to deploy airsloop on virtual env.<o:p></o:p></span></a></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">I created two VMs(libvirt/kvm driven), one for genesis and the other for compute node.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">I authored the site by following these two guides[1][2]. It’s the mix of guide[1] and guide[2].<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">The commands I used are all these ones[3].<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">After fixing several issue, I have deployed the virtual airsloop env.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">I list here some issues I met:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="color:#1F497D;mso-fareast-language:ZH-CN">Node identify failed. At the beginning of step ‘</span><span style="font-size:9.0pt;font-family:"Lucida Console";mso-fareast-language:ZH-CN">prepare_and_deploy_nodes’</span><span style="color:#1F497D;mso-fareast-language:ZH-CN">,
 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.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="color:#1F497D;mso-fareast-language:ZH-CN">My host doesn’t have enough CPU cores, neither the VMs. So I had to increase
</span><span style="font-size:9.0pt;font-family:"Lucida Console";color:#00BF00;mso-fareast-language:ZH-CN">--pods-per-core
</span><span style="color:#1F497D;mso-fareast-language:ZH-CN">in kubelet.yaml. <o:p>
</o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="color:#1F497D;mso-fareast-language:ZH-CN">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’)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="color:#1F497D;mso-fareast-language:ZH-CN">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">I also paste my site changes[4] for reference.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">[1] </span>
<a href="https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html">https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html</a><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">[2] </span>
<a href="https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html">https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html</a><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">[3] </span>
<a href="https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-started">https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-started</a><o:p></o:p></p>
<p class="MsoNormal">[4] <a href="https://github.com/cheng1li/treasuremap/commit/7a8287720dacc6dc1921948aaddec96b8cf2645e">
https://github.com/cheng1li/treasuremap/commit/7a8287720dacc6dc1921948aaddec96b8cf2645e</a><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">Cheng<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span style="mso-fareast-language:ZH-CN">From:</span></b><span style="mso-fareast-language:ZH-CN"> Anirudh Gupta [mailto:Anirudh.Gupta@hsc.com]
<br>
<b>Sent:</b> Thursday, May 30, 2019 7:29 PM<br>
<b>To:</b> 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<br>
<b>Subject:</b> RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-IN">Hi Team,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">I am trying to create Airship-Seaworthy from the link<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"><a href="https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html">https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">Do we need to follow the “Getting Started” section mentioned in Airsloop or will there be any difference in case of Seaworthy.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"><a href="https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-started">https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-started</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">Also what all configurations need to be run from the 3 controller nodes and what needs to be run from 3 computes?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Nirmala UI",sans-serif;color:black;mso-fareast-language:EN-IN">अनिरुद्ध</span></b><b><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">
</span></b><b><span style="font-size:12.0pt;font-family:"Nirmala UI",sans-serif;color:black;mso-fareast-language:EN-IN">गुप्ता</span></b><b><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">(</span><span style="font-size:12.0pt;font-family:"Nirmala UI",sans-serif;color:black;mso-fareast-language:EN-IN">वरिष्ठ</span><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">
</span><span style="font-size:12.0pt;font-family:"Nirmala UI",sans-serif;color:black;mso-fareast-language:EN-IN">अभियंता</span><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">)<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-IN"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="mso-fareast-language:EN-IN">From:</span></b><span style="mso-fareast-language:EN-IN"> Li, Cheng1 <<a href="mailto:cheng1.li@intel.com">cheng1.li@intel.com</a>>
<br>
<b>Sent:</b> 30 May 2019 08:29<br>
<b>To:</b> Anirudh Gupta <<a href="mailto:Anirudh.Gupta@hsc.com">Anirudh.Gupta@hsc.com</a>>;
<a href="mailto:airship-discuss@lists.airshipit.org">airship-discuss@lists.airshipit.org</a>;
<a href="mailto:airship-announce@lists.airshipit.org">airship-announce@lists.airshipit.org</a>;
<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>;
<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
<b>Subject:</b> RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-IN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">I have the same question. I haven’t seen any docs which guides how to deploy airsloop/air-seaworthy in virtual env.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">I am trying to deploy airsloop on libvirt/kvm driven virtual env. Two VMs, one for genesis, the other for compute.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">Virtualbmc for ipmi simulation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">The genesis.sh scripts has been run on genesis node without error. But deploy_site fails at
</span><span style="font-size:9.0pt;font-family:"Lucida Console";mso-fareast-language:ZH-CN">prepare_and_deploy_nodes
</span><span style="color:#1F497D;mso-fareast-language:ZH-CN">task(action ‘set_node_boot’ timeout). I am still investigating this issue.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">It will be great if we have official document for this scenario.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN">Cheng<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="mso-fareast-language:ZH-CN">From:</span></b><span style="mso-fareast-language:ZH-CN"> Anirudh Gupta [<a href="mailto:Anirudh.Gupta@hsc.com">mailto:Anirudh.Gupta@hsc.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2019 3:31 PM<br>
<b>To:</b> <a href="mailto:airship-discuss@lists.airshipit.org">airship-discuss@lists.airshipit.org</a>;
<a href="mailto:airship-announce@lists.airshipit.org">airship-announce@lists.airshipit.org</a>;
<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>;
<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
<b>Subject:</b> [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-IN">Hi Team,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">We want to test Production Ready Airship-Seaworthy in our virtual environment<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">The link followed is<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"><a href="https://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">https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">As per the document we need 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">But we need to deploy our setup on Virtual Environment. Does Airship-Seaworthy support Installation on Virtual Environment?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">We have 2 Rack Servers with Dual-CPU Intel® Xeon® E5 26xx with 16 cores each and 128 GB RAM.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">Is it possible that we can create Virtual Machines on them and set up the complete environment.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">In that case, what possible infrastructure do we require for setting up the complete setup.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN">Looking forward for your response.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">Regards</span><span lang="EN-IN"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Nirmala UI",sans-serif;color:black;mso-fareast-language:EN-IN">अनिरुद्ध</span></b><b><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">
</span></b><b><span style="font-size:12.0pt;font-family:"Nirmala UI",sans-serif;color:black;mso-fareast-language:EN-IN">गुप्ता</span></b><span lang="EN-IN"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">(</span><span style="font-size:12.0pt;font-family:"Nirmala UI",sans-serif;color:black;mso-fareast-language:EN-IN">वरिष्ठ</span><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">
</span><span style="font-size:12.0pt;font-family:"Nirmala UI",sans-serif;color:black;mso-fareast-language:EN-IN">अभियंता</span><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">)</span><span lang="EN-IN"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-IN">Hughes Systique Corporation</span><span lang="EN-IN"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;background:white;mso-fareast-language:EN-IN">D-23,24 Infocity II, Sector 33, Gurugram, Haryana 122001</span><span lang="EN-IN"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN" style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:ZH-CN">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IN" style="font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:ZH-CN">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.
<o:p></o:p></span></p>
</div>
</body>
</html>