Re: [openstack-dev] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments

2018-08-30 Thread Julia Kreger
Greetings everyone,

It looks like the most agreeable time on the doodle[1] seems to be
Tuesday September 4th at 13:00 UTC. Are there any objections to using
this time?

If not, I'll go ahead and create an etherpad, and setup a bluejeans
call for that time to enable high bandwidth discussion.

-Julia
[1]: https://doodle.com/poll/y355wt97heffvp3m

On Mon, Aug 27, 2018 at 9:53 AM Julia Kreger
 wrote:
>
> Greetings everyone!
>
> We in Ironic land would like to go into the PTG with some additional
> thoughts, requirements, and ideas as it relates to distributed and
> geographically distributed deployments.
>
[trim]

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments

2018-08-27 Thread Julia Kreger
Greetings everyone!

We in Ironic land would like to go into the PTG with some additional
thoughts, requirements, and ideas as it relates to distributed and
geographically distributed deployments.

As you may or may not know, we did take a first step towards
supporting some of the architectures needed with conductor_groups this
past cycle, but we have two very distinct needs that have been
expressed with-in the community.

1) Need to federate and share baremetal resources between ironic
deployments. A specification[1] was proposed to try and begin to
capture what this would look like ironic wise. At a high level, this
would look like an ironic node that actually consumes and remotely
manages a node via another ironic deployment. Largely this would be a
stand-alone user/admin user deployment cases, where hardware inventory
insight is needed.

2) Need to securely manage remote sites with different security
postures, while not exposing control-plane components as an attack
surface. Some early discussion into this would involve changing
Conductor/IPA communication flow[2], or at least supporting a
different model, and some sort of light weight intermediate middle-man
service that helps facilitate the local site management.

With that in mind, we would like to schedule a call for sometime next
week where we can kind of talk through and discuss these thoughts and
needs in real time in advance of the PTG so we can be even better
prepared. We are attempting to identify a time with a doodle[3].
Please select a time and date, so we can schedule something for next
week.

Thanks,

-Julia

[1]: https://review.openstack.org/#/c/560152/
[2]: https://review.openstack.org/212206
[3]: https://doodle.com/poll/y355wt97heffvp3m

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev