<div dir="ltr">It is not a big worry but it would have been better if overcloud nodes to be independent of undercloud except being a manager. Think the use case where:<div><br></div><div>1. nova has three region, geographically apart</div>
<div>2. geographical area hosting undercloud gets doomed</div><div>3. all region of nova gets affected as they can not reboot</div><div><br></div><div>But, we can leave operator to ensure undercloud comes backend. Or, am I thinking too much?</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 28, 2014 at 10:47 AM, James Polley <span dir="ltr"><<a href="mailto:jp@jamezpolley.com" target="_blank">jp@jamezpolley.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">That is correct, we intend that the undercloud should be designed with HA in mind.<br><br>In terms of the design of TripleO, the devtest.sh implementation aims to have this available as a default (see <a href="http://docs.openstack.org/developer/tripleo-incubator/README.html#stage-2-being-worked-on" target="_blank">http://docs.openstack.org/developer/tripleo-incubator/README.html#stage-2-being-worked-on</a> for some dated and very brief notes about our aims). This is something that's been receiving a lot of attention over the last cycle, but it's not quite ready out-of-the-box yet.<br>
<br>In terms of implementation, this will still require the implementor to make sure that their implementation meets their needs for HA. For instance, it doesn't matter how many redundant neutron nodes we run if they all hang off the back of a single physical non-redundant switch...<div>
<br></div><div>Are there particular concerns you have with this design?<div><div class="h5"><br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 28, 2014 at 2:20 PM, Jyoti Ranjan <span dir="ltr"><<a href="mailto:jranjan@gmail.com" target="_blank">jranjan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I do agree but it create an extra requirement for Undercloud if we high availability is important criteria. Because of this, undercloud has to be there 24x7, 365 days and to make it available we need to have HA for this also. So, you indirectly mean that undercloud also should be designed keeping high availability in mind.
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 7:53 PM, Ben Nemec <span dir="ltr"><<a href="mailto:openstack@nemebean.com" target="_blank">openstack@nemebean.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">We probably will at some point, but I don't know that it's a huge<br>
priority right now. The PXE booting method works fine, and as I<br>
mentioned we don't intend you to reboot machines without using the<br>
undercloud anyway, just like Nova doesn't expect you to reboot vms<br>
directly via libvirt (or your driver of choice).<br>
<br>
It's likely there would be other issues booting a deployed machine if<br>
the undercloud is down anyway (nothing to respond to DHCP requests, for<br>
one), so I don't see that as something we want to encourage anyway.<br>
<span><font color="#888888"><br>
-Ben<br>
</font></span><div><br>
On 08/27/2014 04:11 AM, Jyoti Ranjan wrote:<br>
> I believe that local boot option is available in Ironic. Will not be a good<br>
> idea to boot from local disk instead of relying on PXE boot always? Curious<br>
> to know why we are not going this path?<br>
><br>
><br>
> On Wed, Aug 27, 2014 at 3:54 AM, 严超 <<a href="mailto:yanchao727@gmail.com" target="_blank">yanchao727@gmail.com</a>> wrote:<br>
><br>
>> Thank you very much.<br>
>> And sorry for the cross-posting.<br>
>><br>
</div><div><div>>> *Best Regards！*<br>
>><br>
>><br>
>> *Chao Yan--------------**My twitter：Andy Yan @yanchao727<br>
>> <<a href="https://twitter.com/yanchao727" target="_blank">https://twitter.com/yanchao727</a>>*<br>
>><br>
>><br>
>> *My Weibo：<a href="http://weibo.com/herewearenow" target="_blank">http://weibo.com/herewearenow</a><br>
>> <<a href="http://weibo.com/herewearenow" target="_blank">http://weibo.com/herewearenow</a>>--------------*<br>
>><br>
>><br>
>> 2014-08-26 23:17 GMT+08:00 Ben Nemec <<a href="mailto:openstack@nemebean.com" target="_blank">openstack@nemebean.com</a>>:<br>
>><br>
>> Oh, after writing my response below I realized this is cross-posted<br>
>>> between openstack and openstack-dev. Please don't do that.<br>
>>><br>
>>> I suppose this probably belongs on the users list, but since I've<br>
>>> already written the response I guess I'm not going to argue too much. :-)<br>
>>><br>
>>> On 08/26/2014 07:36 AM, 严超 wrote:<br>
>>>> Hi, All:<br>
>>>> I've deployed undercloud and overcloud on some baremetals. All<br>
>>>> overcloud machines are deployed by undercloud.<br>
>>>> Then I tried to shutdown undercloud machines. After that, if I<br>
>>>> reboot one overcloud machine, it will never boot from net, AKA PXE used<br>
>>> by<br>
>>>> undercloud.<br>
>>><br>
>>> Yes, that's normal. With the way our baremetal deployments work today,<br>
>>> the deployed systems always PXE boot. After deployment they PXE boot a<br>
>>> kernel and ramdisk that use the deployed hard disk image, but it's still<br>
>>> a PXE boot.<br>
>>><br>
>>>> Is that what TripleO is designed to be ? We can never shutdown<br>
>>>> undercloud machines for maintainance of overcloud ? Please help me<br>
>>>> clearify that.<br>
>>><br>
>>> Yes, that's working as intended at the moment. I recall hearing that<br>
>>> there were plans to eliminate the PXE requirement after deployment, but<br>
>>> you'd have to talk to the Ironic team about that.<br>
>>><br>
>>> Also, I don't think it was ever the intent of TripleO that the<br>
>>> undercloud would be shut down after deployment. The idea is that you<br>
>>> use the undercloud to manage the overcloud machines, so if you want to<br>
>>> reboot one you do it via the undercloud nova, not directly on the system<br>
>>> itself.<br>
>>><br>
>>>><br>
>>>> *Best Regards！*<br>
>>>><br>
>>>><br>
>>>> *Chao Yan--------------**My twitter：Andy Yan @yanchao727<br>
>>>> <<a href="https://twitter.com/yanchao727" target="_blank">https://twitter.com/yanchao727</a>>*<br>
>>>><br>
>>>><br>
>>>> *My Weibo：<a href="http://weibo.com/herewearenow" target="_blank">http://weibo.com/herewearenow</a><br>
>>>> <<a href="http://weibo.com/herewearenow" target="_blank">http://weibo.com/herewearenow</a>>--------------*<br>
>>>><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> OpenStack-dev mailing list<br>
>>>> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> OpenStack-dev mailing list<br>
>>> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
><br>
<br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div></div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>