Hi Aleksey,
> What is the status of making networking part replaceable? As I know, [0]
> is in progress. Are there any other activities in progress (about API,
> serialization for orchestrator, network verification)? Do we have specs on
> review (I know about this one: [1]) ?
>
>
AFAIK there
>
>
> It's used in stop_deployment provision stage [0] and for control reboot
> [1].
>
> > Is it a fall back mechanism if the mcollective fails?
>
> Yes it's like fall back mechanism, but it's used always [2].
>
As I remember it the use of SSH for stopping provisioning was because of
our use of
/#/q/Iff947f0053577f19441c04101e5a35a7820e40a0,n,z
[5]
https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series
Thanks,
Ryan
On Tue, Mar 10, 2015 at 4:20 AM, Tomasz Napierala tnapier...@mirantis.com
wrote:
On 09 Mar 2015, at 18:21, Ryan Moe r
Hi All,
I've noticed a few times recently where reviews have been abandoned by
people who were not the original authors. These reviews were only days old
and there was no prior notice or discussion. This is both rude and
discouraging to contributors. Reasons for abandoning should be discussed on
Dmitriy,
Thank you for the excellent run-down of the CLI commands. I assume this
will make its way into the developer documentation? I would like to know if
you could point me to more information about the inner workings of granular
deployment. Currently it's challenging to debug issues related
Could this be caused by a case mismatch between the MAC address as it
exists in the database and the MAC that comes from the agent?
When the interfaces are updated with data from the agent we attempt to
match the MAC to an existing interface (
