[Starlingx-discuss] Six in a box - Meetings and Status + Packet

[Curtis]

On Thu, May 16, 2019 at 2:45 PM Martinez Landa, Hayde <
hayde.martinez.landa at intel.com> wrote:

> Hi All,
>
>
>
> We had our bi-weekly meeting Today,
>
> So far the script is able to create the VM without keyboard interaction,
>
> Guillermo was working on this, but due to his new responsibilities he
> transferred all to me.
>
>
>
> The repo is based on the automation suite from the GDC QA team, they are
> planning to release the code,
>
> When they do, we will release our code too.
>
>
>
> Also, due to release gating priorities, this project is being paused,
> therefore the meetings will be canceled.
>
> The meeting info was removed from the Wiki, but updates will still be
> posted on the project etherpad [0].
>
>
>
> We discussed that having a script that provides an installation for
> testing was step 1, but we can have a step 0
>
> Which could be a Packet instance, on this subject we discussed Today with
> Curtis about the current implementation
>
> For Packet; we would like to know:
>

Thanks Hayde.


>
>
>    - How can we help on this effort?
>
>
Well, basically we identify your use case and then work to get it running.
:)  When you say step 1 what are you thinking?



>
>    -
>    - Is there something already being work on or where are we right now
>    about the Packet initiative?
>
>
There's a couple things on the go:

1) I've documented some of the ipxe install for packet.com:
https://wiki.openstack.org/wiki/StarlingX/StarlingX_Packet.com_iPXE_Installation
2) I wrote a bunch of Ansible to create packet nodes and setup a hypervisor
so that stx could be run in a vm:
https://github.com/ccollicutt/starlingx-workshop
3) We should probably setup a demo system of some kind

I think one thing we need to do is expand the ipxe install and set it up so
that the post install configuration can be run. I guess that's Ansible
based now so it might be easier; may need to align with existing deployment
mechanisms. There is probably some tweaking we need to do with the ipxe and
packet environment...packet.com is layer 3 only by default. It does support
vlans so a proper environment would need to be setup to have a place to
deploy stx.

Thanks,
Curtis



>
>    -
>
>
>
> [0] https://etherpad.openstack.org/p/stx-inabox
>
>
>
>
>
> Best,
>
> Haydé
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>


-- 
Blog: serverascode.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190516/742c2ff8/attachment.html>