[rdo-list] Packstack refactor and future ideas

[Boris Derzhavets]

________________________________
From: rdo-list-bounces at redhat.com <rdo-list-bounces at redhat.com> on behalf of Adam Young <ayoung at redhat.com>
Sent: Thursday, June 9, 2016 10:12 AM
To: rdo-list at redhat.com
Subject: Re: [rdo-list] Packstack refactor and future ideas

On 06/08/2016 07:05 PM, Ivan Chavero wrote:
>
> ----- Original Message -----
>> From: "Alan Pevec" <apevec at redhat.com>
>> To: "Ivan Chavero" <ichavero at redhat.com>
>> Cc: "rdo-list" <rdo-list at redhat.com>
>> Sent: Wednesday, June 8, 2016 5:48:07 PM
>> Subject: Re: [rdo-list] Packstack refactor and future ideas
>>
>>> I don't agree with this, we can set the untested features as "experimental"
>> or "unsupported"
>>
>> Best is to remove them to make that clear, because no matter what
>> deprecation warnings you put[*] people will keep using features until
>> they're gone, giving us bug reports to take care of and without CI to
>> verify fixes.
>> It's long-term maintenance burden I am concerned about, for features
>> which are clearly out of scope.
> I understand this, my concern is that if we remove this feature we will leave
> users with no tool for doing multinode in a lightweight way and this might
> drive off users from testing/adopting RDO.

I think it is starting to have the opposite effect.  Packstack, being
available, gives the wrong idea about RDO:  you are supposed to install
bare metal.

The Tripleo Quickstart approach is that everything is in a VM.

     Sorry , if I am asking stupid question , but in meantime TripleO QuickStart
     configuration been generated on VIRTHOST is not persistent between cold
     reboots.  As soon as I shutdown UNDERCLOUD VM (as stack) it's gone for ever.
     Packstack deployments  on usual VMs driven by KVM/Libvirt are persistent
     between cold reboots.  I don't have to start every morning from scratch
     Am I missing something in current TripleO QuickStart status ?

  Thanks.
  Boris.



Packstack is doing too much:  image building, provision, and running the
system.

A better approach would be to have our tooling set out so that a user
can build their own images, and then deploy to a VM.  OR better yet, a
container.


We need to drive on to Kolla.


Kolla as the Controller for Tripleo and Kolla running in a VM and Kolla
running on my desktop should all be close enough to identical to avoid
the fragmentation we have now.






>
> I'm willing to create CI tests for multinode Packstack in order to maintain
> this features.
>
> And believe me it would be easier for me just to drop this features but i really
> think users are benefiting from this features.
>
> Cheers,
> Ivan
>
> _______________________________________________
> rdo-list mailing list
> rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
rdo-list Info Page - Red Hat<https://www.redhat.com/mailman/listinfo/rdo-list>
www.redhat.com
The rdo-list mailing list provides a forum for discussions about installing, running, and using OpenStack on Red Hat based distributions. To see the collection of ...


>
> To unsubscribe: rdo-list-unsubscribe at redhat.com


_______________________________________________
rdo-list mailing list
rdo-list at redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list

To unsubscribe: rdo-list-unsubscribe at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20160609/571a8cab/attachment.html>