Re: [openstack-dev] [ironic] Tenks

2018-10-08 Thread Jim Rollenhagen 
On Tue, Oct 2, 2018 at 8:59 AM Mark Goddard  wrote:

> Hi,
>
> In the most recent Ironic meeting we discussed [1] tenks, and the
> possibility of adding the project under Ironic governance. We agreed to
> move the discussion to the mailing list. I'll introduce the project here
> and give everyone a chance to ask questions. If things appear to move in
> the right direction, I'll propose a vote for inclusion under Ironic's
> governance.
>
> Tenks is a project for managing 'virtual bare metal clusters'. It aims to
> be a drop-in replacement for the various scripts and templates that exist
> in the Ironic devstack plugin for creating VMs to act as bare metal nodes
> in development and test environments. Similar code exists in Bifrost and
> TripleO, and probably other places too. By focusing on one project, we can
> ensure that it works well, and provides all the features necessary as
> support for bare metal in the cloud evolves.
>
> That's tenks the concept. Tenks in reality today is a working version 1.0,
> written in Ansible, built by Will Miller (w-miller) during his summer
> placement. Will has returned to his studies, and Will Szumski (jovial) has
> picked it up. You don't have to be called Will to work on Tenks, but it
> helps.
>
> There are various resources available for anyone wishing to find out more:
>
> * Ironic spec review: https://review.openstack.org/#/c/579583
> * Documentation: https://tenks.readthedocs.io/en/latest/
> * Source code: https://github.com/stackhpc/tenks
> * Blog: https://stackhpc.com/tenks.html
> * IRC: mgoddard or jovial in #openstack-ironic
>
> What does everyone think? Is this something that the ironic community
> could or should take ownership of?
>

Makes sense to me, but we should also have an explicit goal of using tenks
to kill our devstack code (and the other things mentioned).

Consider me +2 on the spec but leaving time for additional discussion. :)

Thanks Mark!

// jim


>
> [1]
> http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-10-01-15.00.log.html#l-170
>
> Thanks,
> Mark
> __
> 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 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

Re: [openstack-dev] [ironic] Tenks

2018-10-03 Thread Julia Kreger 
On Wed, Oct 3, 2018 at 9:17 AM Mark Goddard  wrote:

>
>
> On Wed, 3 Oct 2018 at 17:10, James LaBarre  wrote:
>
>> On 10/2/18 10:37 AM, Mark Goddard wrote:
>>
>>
>>
>> On Tue, 2 Oct 2018 at 14:03, Jay Pipes  wrote:
>>
>>> On 10/02/2018 08:58 AM, Mark Goddard wrote:
>>> > Tenks is a project for managing 'virtual bare metal clusters'. It aims
>>> > to be a drop-in replacement for the various scripts and templates that
>>> > exist in the Ironic devstack plugin for creating VMs to act as bare
>>> > metal nodes in development and test environments. Similar code exists
>>> in
>>> > Bifrost and TripleO, and probably other places too. By focusing on one
>>> > project, we can ensure that it works well, and provides all the
>>> features
>>> > necessary as support for bare metal in the cloud evolves.
>>>
>>> How does Tenks relate to OVB?
>>>
>>>
>>> https://openstack-virtual-baremetal.readthedocs.io/en/latest/introduction.html
>>
>>
>> Good question. As far as I'm aware, OVB is a tool for using an OpenStack
>> cloud to host the virtual bare metal nodes, and is typically used for
>> testing TripleO. Tenks does not rule out supporting this use case in
>> future, but currently operates more like the Ironic devstack plugin, using
>> libvirt/KVM/QEMU as the virtualisation provider.
>>
>>
>> I'm presuming, as Tenks is supposed to support multiple hypervisors, that
>> a multi-arch environment would be supported (different node types on
>> different architectures).  Or does this even enter into the consideration?
>>
>
> I think that would be a good feature to consider in future, although it's
> not something that works currently.
>

I think it would be a very important thing to have as we branch out into
different architectures. I would personally love to see an ARM64 CI job. To
actually put that job in place would mean major changes to VM creation
which would be beneficial to put in one place. Long story short, I'm all
for additional spoons.

> __
>> 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 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 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

Re: [openstack-dev] [ironic] Tenks

2018-10-03 Thread Mark Goddard 
On Wed, 3 Oct 2018 at 17:10, James LaBarre  wrote:

> On 10/2/18 10:37 AM, Mark Goddard wrote:
>
>
>
> On Tue, 2 Oct 2018 at 14:03, Jay Pipes  wrote:
>
>> On 10/02/2018 08:58 AM, Mark Goddard wrote:
>> > Tenks is a project for managing 'virtual bare metal clusters'. It aims
>> > to be a drop-in replacement for the various scripts and templates that
>> > exist in the Ironic devstack plugin for creating VMs to act as bare
>> > metal nodes in development and test environments. Similar code exists
>> in
>> > Bifrost and TripleO, and probably other places too. By focusing on one
>> > project, we can ensure that it works well, and provides all the
>> features
>> > necessary as support for bare metal in the cloud evolves.
>>
>> How does Tenks relate to OVB?
>>
>>
>> https://openstack-virtual-baremetal.readthedocs.io/en/latest/introduction.html
>
>
> Good question. As far as I'm aware, OVB is a tool for using an OpenStack
> cloud to host the virtual bare metal nodes, and is typically used for
> testing TripleO. Tenks does not rule out supporting this use case in
> future, but currently operates more like the Ironic devstack plugin, using
> libvirt/KVM/QEMU as the virtualisation provider.
>
>
> I'm presuming, as Tenks is supposed to support multiple hypervisors, that
> a multi-arch environment would be supported (different node types on
> different architectures).  Or does this even enter into the consideration?
>

I think that would be a good feature to consider in future, although it's
not something that works currently.

> __
> 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 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

Re: [openstack-dev] [ironic] Tenks

2018-10-03 Thread James LaBarre 

On 10/2/18 10:37 AM, Mark Goddard wrote:



On Tue, 2 Oct 2018 at 14:03, Jay Pipes > wrote:


On 10/02/2018 08:58 AM, Mark Goddard wrote:
> Tenks is a project for managing 'virtual bare metal clusters'.
It aims
> to be a drop-in replacement for the various scripts and
templates that
> exist in the Ironic devstack plugin for creating VMs to act as bare
> metal nodes in development and test environments. Similar code
exists in
> Bifrost and TripleO, and probably other places too. By focusing
on one
> project, we can ensure that it works well, and provides all the
features
> necessary as support for bare metal in the cloud evolves.

How does Tenks relate to OVB?


https://openstack-virtual-baremetal.readthedocs.io/en/latest/introduction.html


Good question. As far as I'm aware, OVB is a tool for using an 
OpenStack cloud to host the virtual bare metal nodes, and is typically 
used for testing TripleO. Tenks does not rule out supporting this use 
case in future, but currently operates more like the Ironic devstack 
plugin, using libvirt/KVM/QEMU as the virtualisation provider.



I'm presuming, as Tenks is supposed to support multiple hypervisors, 
that a multi-arch environment would be supported (different node types 
on different architectures).  Or does this even enter into the 
consideration?


__
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

Re: [openstack-dev] [ironic] Tenks

2018-10-02 Thread Mark Goddard 
On Tue, 2 Oct 2018 at 14:03, Jay Pipes  wrote:

> On 10/02/2018 08:58 AM, Mark Goddard wrote:
> > Hi,
> >
> > In the most recent Ironic meeting we discussed [1] tenks, and the
> > possibility of adding the project under Ironic governance. We agreed to
> > move the discussion to the mailing list. I'll introduce the project here
> > and give everyone a chance to ask questions. If things appear to move in
> > the right direction, I'll propose a vote for inclusion under Ironic's
> > governance.
> >
> > Tenks is a project for managing 'virtual bare metal clusters'. It aims
> > to be a drop-in replacement for the various scripts and templates that
> > exist in the Ironic devstack plugin for creating VMs to act as bare
> > metal nodes in development and test environments. Similar code exists in
> > Bifrost and TripleO, and probably other places too. By focusing on one
> > project, we can ensure that it works well, and provides all the features
> > necessary as support for bare metal in the cloud evolves.
> >
> > That's tenks the concept. Tenks in reality today is a working version
> > 1.0, written in Ansible, built by Will Miller (w-miller) during his
> > summer placement. Will has returned to his studies, and Will Szumski
> > (jovial) has picked it up. You don't have to be called Will to work on
> > Tenks, but it helps.
> >
> > There are various resources available for anyone wishing to find out
> more:
> >
> > * Ironic spec review: https://review.openstack.org/#/c/579583
> > * Documentation: https://tenks.readthedocs.io/en/latest/
> > * Source code: https://github.com/stackhpc/tenks
> > * Blog: https://stackhpc.com/tenks.html
> > * IRC: mgoddard or jovial in #openstack-ironic
> >
> > What does everyone think? Is this something that the ironic community
> > could or should take ownership of?
>
> How does Tenks relate to OVB?
>
>
> https://openstack-virtual-baremetal.readthedocs.io/en/latest/introduction.html


Good question. As far as I'm aware, OVB is a tool for using an OpenStack
cloud to host the virtual bare metal nodes, and is typically used for
testing TripleO. Tenks does not rule out supporting this use case in
future, but currently operates more like the Ironic devstack plugin, using
libvirt/KVM/QEMU as the virtualisation provider.


>
> Best,
> -jay
>
> __
> 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 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

Re: [openstack-dev] [ironic] Tenks

2018-10-02 Thread Jay Pipes 

On 10/02/2018 08:58 AM, Mark Goddard wrote:

Hi,

In the most recent Ironic meeting we discussed [1] tenks, and the 
possibility of adding the project under Ironic governance. We agreed to 
move the discussion to the mailing list. I'll introduce the project here 
and give everyone a chance to ask questions. If things appear to move in 
the right direction, I'll propose a vote for inclusion under Ironic's 
governance.


Tenks is a project for managing 'virtual bare metal clusters'. It aims 
to be a drop-in replacement for the various scripts and templates that 
exist in the Ironic devstack plugin for creating VMs to act as bare 
metal nodes in development and test environments. Similar code exists in 
Bifrost and TripleO, and probably other places too. By focusing on one 
project, we can ensure that it works well, and provides all the features 
necessary as support for bare metal in the cloud evolves.


That's tenks the concept. Tenks in reality today is a working version 
1.0, written in Ansible, built by Will Miller (w-miller) during his 
summer placement. Will has returned to his studies, and Will Szumski 
(jovial) has picked it up. You don't have to be called Will to work on 
Tenks, but it helps.


There are various resources available for anyone wishing to find out more:

* Ironic spec review: https://review.openstack.org/#/c/579583
* Documentation: https://tenks.readthedocs.io/en/latest/
* Source code: https://github.com/stackhpc/tenks
* Blog: https://stackhpc.com/tenks.html
* IRC: mgoddard or jovial in #openstack-ironic

What does everyone think? Is this something that the ironic community 
could or should take ownership of?


How does Tenks relate to OVB?

https://openstack-virtual-baremetal.readthedocs.io/en/latest/introduction.html

Best,
-jay

__
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] Tenks

2018-10-02 Thread Mark Goddard 
Hi,

In the most recent Ironic meeting we discussed [1] tenks, and the
possibility of adding the project under Ironic governance. We agreed to
move the discussion to the mailing list. I'll introduce the project here
and give everyone a chance to ask questions. If things appear to move in
the right direction, I'll propose a vote for inclusion under Ironic's
governance.

Tenks is a project for managing 'virtual bare metal clusters'. It aims to
be a drop-in replacement for the various scripts and templates that exist
in the Ironic devstack plugin for creating VMs to act as bare metal nodes
in development and test environments. Similar code exists in Bifrost and
TripleO, and probably other places too. By focusing on one project, we can
ensure that it works well, and provides all the features necessary as
support for bare metal in the cloud evolves.

That's tenks the concept. Tenks in reality today is a working version 1.0,
written in Ansible, built by Will Miller (w-miller) during his summer
placement. Will has returned to his studies, and Will Szumski (jovial) has
picked it up. You don't have to be called Will to work on Tenks, but it
helps.

There are various resources available for anyone wishing to find out more:

* Ironic spec review: https://review.openstack.org/#/c/579583
* Documentation: https://tenks.readthedocs.io/en/latest/
* Source code: https://github.com/stackhpc/tenks
* Blog: https://stackhpc.com/tenks.html
* IRC: mgoddard or jovial in #openstack-ironic

What does everyone think? Is this something that the ironic community could
or should take ownership of?

[1]
http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-10-01-15.00.log.html#l-170

Thanks,
Mark
__
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