: Re: [openstack-dev] [sahara] summit wrap-up: subprojects
- Original Message -
> the image-elements is too unstable to be used by anyone but an expert at
> this point. imho we should make sure the experts produce working images
> first, it's what our users will need in the
- Original Message -
> the image-elements is too unstable to be used by anyone but an expert at
> this point. imho we should make sure the experts produce working images
> first, it's what our users will need in the first place, then make the
> image generation more stable.
+1
mike
___
On 05/29/2014 10:15 AM, Michael McCune wrote:
- Original Message -
Re sahara-image-elements we found a bunch of issues that we should
solve and that's why I think that keeping current releasing is still
the best option.
- we should test it better and depend on stable diskimage-builder
what were the bunch of issues you ran into? will you capture them in a
blueprint or bug so they can be resolved?
best,
matt
On 05/29/2014 10:03 AM, Sergey Lukjanov wrote:
Re sahara-image-elements we found a bunch of issues that we should
solve and that's why I think that keeping current rele
- Original Message -
> Re sahara-image-elements we found a bunch of issues that we should
> solve and that's why I think that keeping current releasing is still
> the best option.
>
> - we should test it better and depend on stable diskimage-builder version
> The dib is now published to
- Original Message -
> > > sahara-extra
> >
> > Keep it as is, no need to stop releasing, because we're not publishing
> > anything to pypi. No real need for tags.
>
> Even if we keep the repo for now, I think we could simplify a little
> bit. The edp-examples could be moved to the Sah
below, sahara-extra
On Wed, 2014-05-28 at 20:02 +0400, Sergey Lukjanov wrote:
> Hey folks,
>
> it's a small wrap-up for the topic "Sahara subprojects releasing and
> versioning" that was discussed partially on summit and requires some
> more discussions. You can find details in [0].
>
> > common
> client
We have separated launchpad project for client and we're publishing
client releases to it.
> extra
I'm neutral about moving job examples and API samples between sahara and extra
> ui tests
if we'll be able to remove sahara-dashboard before good integration
tests for our pages will be
On 05/29/2014 09:59 AM, Trevor McKay wrote:
below, sahara-extra
sahara-extra
Keep it as is, no need to stop releasing, because we're not publishing
anything to pypi. No real need for tags.
Even if we keep the repo for now, I think we could simplify a little
bit. The edp-examples could be
Re sahara-image-elements we found a bunch of issues that we should
solve and that's why I think that keeping current releasing is still
the best option.
- we should test it better and depend on stable diskimage-builder version
The dib is now published to pypi, so, we could make
sahara-image-elemen
On 05/29/2014 07:23 AM, Alexander Ignatov wrote:
On 28 May 2014, at 20:02, Sergey Lukjanov wrote:
sahara-image-elements
We're agreed that some common parts should be merged into the
diskimage-builder repo (like java support, ssh, etc.). The main issue
of keeping -image-elements separated is
On 28 May 2014, at 20:02, Sergey Lukjanov wrote:
> Hey folks,
>
> it's a small wrap-up for the topic "Sahara subprojects releasing and
> versioning" that was discussed partially on summit and requires some
> more discussions. You can find details in [0].
>
>> common
>
> We'll include only one
On 05/28/2014 12:02 PM, Sergey Lukjanov wrote:
Hey folks,
it's a small wrap-up for the topic "Sahara subprojects releasing and
versioning" that was discussed partially on summit and requires some
more discussions. You can find details in [0].
common
We'll include only one tarball for sahara
Hey folks,
it's a small wrap-up for the topic "Sahara subprojects releasing and
versioning" that was discussed partially on summit and requires some
more discussions. You can find details in [0].
> common
We'll include only one tarball for sahara to the release launchpad
pages. All other links w
14 matches
Mail list logo
