[OpenStack-Infra] [third-party][openstack][CI] Examples required for "single_node_ci_data.yaml" config file

[Abhishek Shrivastava]

Hi Folks,

I have been configuring the new OpenStack CI and was not able to figure out
what exactly needed to be put in the section "*oscc_file_contents:*". So,
if anyone has done the configuration and is running the new OpenStack CI
please let me know what to put in the configuration.

Also, need to know how to add slaves to Jenkins using the Nodepool images.

-- 


*Thanks & Regards,*
*Abhishek*
*Cloudbyte Inc. *
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] [third-party][openstack][CI] Examples required for "single_node_ci_data.yaml" config file

[Abhishek Shrivastava]

Hi Folks,

I have been configuring the new OpenStack CI and was not able to figure out
what exactly needed to be put in the section "*oscc_file_contents:*". So,
if anyone has done the configuration and is running the new OpenStack CI
please let me know what to put in the configuration.

Also, need to know how to add slaves to Jenkins using the Nodepool images.

-- 


*Thanks & Regards,*
*Abhishek*
*Cloudbyte Inc. *
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] [Infra] Meeting Tuesday May 10th at 19:00 UTC

[Elizabeth K. Joseph]

Hi everyone,

The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday May 10th, at 19:00 UTC in #openstack-meeting

Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting

Anyone is welcome to to add agenda items and everyone interested in
the project infrastructure and process surrounding automated testing
and deployment is encouraged to attend.

In case you missed it or would like a refresher, the meeting minutes
and full[0] logs from our last meeting are available:

Minutes: 
http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-05-03-19.02.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-05-03-19.02.txt
Log: 
http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-05-03-19.02.log.html

[0] The meeting became a bit disjointed when we had a netsplit, so
these logs and minutes reflect the bot's side of the netsplit, fungi
may provide logs from his side of the split ;)

-- 
Elizabeth Krumbach Joseph || Lyz || pleia2

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Tools for tracking the Scientific WG

[Blair Bethwaite]

Hi Jeremy,

On 10 May 2016 at 03:25, Jeremy Stanley  wrote:
> Worth noting, Storyboard does have kanban functionality similar to
> that. It calls them "worklists" (simple) or "boards" (customizable
> multi-lane) but they're the same sort of card organizing system.

I thought so as I quickly found the list functionality... But tbh I
find the interface somewhat confusing and could not, after another 5
minutes just now, figure out how to add items to a list... they seem
to have to exist as "tasks" or "stories" already, but I can't figure
out how to create a "task" (or perhaps what the difference between a
"task and a "story" is?), and "stories" seem to have to be part of a
project, but I can't create a project...?

-- 
Cheers,
~Blairo

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] binary package install - plan of attack

[Robert Collins]

On 9 May 2016 9:20 PM, "Andreas Jaeger"  wrote:

>
> And then invoke "bindep test" and that would install both packages,
correct?

Yes.

> In that case our three steps here would be:
> * Mark in the reviews some of the dependencies as [test]
> * Invoke "bindep test" instead of "bindep" in infra scripts
> * Fix the bug (not a blocking issue)

Yes.
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Tools for tracking the Scientific WG

[Jeremy Stanley]

On 2016-05-09 23:08:17 +1000 (+1000), Blair Bethwaite wrote:
[...]
> If that's true, then I think I'd prefer to just use trello as a
> light-weight tracker & coordinator and items can get fleshed out
> further in other places as appropriate. How do you feel about that?

Worth noting, Storyboard does have kanban functionality similar to
that. It calls them "worklists" (simple) or "boards" (customizable
multi-lane) but they're the same sort of card organizing system.
-- 
Jeremy Stanley

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Tools for tracking the Scientific WG

[Blair Bethwaite]

Hi Stig, hi all,

On 6 May 2016 at 18:41, Stig Telfer  wrote:
> One possibility I’m considering for mapping tasks and tracking progress on 
> the activities of the working group would be to use Storyboard.  As I 
> understand it the Infra team use Storyboard, can anyone comment from 
> experience on whether Storyboard would be a good choice for tracking the 
> activities of a working group?

How confident are you that storyboard fits here? I haven't tried to
use it before and don't really know anything much about it, but I did
have a 10 sec look and it seems like it has been designed as a kind of
task and epic tracking/coordination tool for OpenStack dev type
activities - would that be fair? One immediate impression I get from
it is that it has a view of the world (versus just a plain list making
tool), and I'm not entirely sure this will fit with the (potentially
many and varied) activities of a working group. It might be suitable
for some of them, but probably not all? I couldn't immediately figure
out how to create trello-like lists of cards (can't seem to create
arbitrary cards).

If that's true, then I think I'd prefer to just use trello as a
light-weight tracker & coordinator and items can get fleshed out
further in other places as appropriate. How do you feel about that?

-- 
Cheers,
~Blairo

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] binary package install - plan of attack

[Andreas Jaeger]

On 2016-05-09 11:11, Robert Collins wrote:
> On 9 May 2016 at 20:43, Andreas Jaeger  wrote:
>> On 2016-05-09 10:29, Robert Collins wrote:
>>> On 30 April 2016 at 09:00, Andreas Jaeger  wrote:
 Paul and myself discussed this morning how to move forward with binary
 package installation - the bindep-fallback.txt/other-requirements.txt 
 story.

 I wrote up what we discussed and hope I didn't forgot anything here. Please
 review and comment - and sign up if you want to help.

 Andreas - who will board his plane to Washington in a few minutes

 Goals:
 1. bindep-fallback.txt should be minimal and handle packages that the
majority of projects need.
 2. Projects can use other-requirements to document their binary
requirements.
 3. There are no apt-get/yum install commands in jenkins/jobs/

 Proposal:

 1. Resolve with lifeless how the other-requirements.txt file should
look like, see:
nova: https://review.openstack.org/#/c/200672/
swift: https://review.openstack.org/#/c/298313/
>>>
>>> I'm not sure what resolving is needed? the only outstanding question I
>>
>> With resolving I meant: Figure out how the entries should look like and
>> whether we need to invoke bindep differently - and whether bindep needs
>> a fix.
>>
>>> saw there was whether the default profile was always active - it is.
>>>
>>> The issue I mention with bindep is that
>>>
>>> foo[platform:dpkg test]
>>>
>>> Will default on on dpkg platforms, because one of the profiles is
>>> active - but it shouldn't, because there are other user profiles
>>> listed. The rule should be 'A thing is in the default profile if all
>>> the profiles listed are automatic profiles, otherwise it is not in the
>>> default profile'.
>>
>> So, how should we write the files?
> 
> Testing only dependencies should be in the test profile.
> 
> We may want to have a source or similar named profile for
> building-from-source of things, but I'd start with just the default
> profile for the always-needed deps and test for CI test run
> dependencies.

Yes, start small...

>> Should they have [test] for everything in it? In that case, we would
>> need to invoke the test profile in bindep and fix bindep to handle the
>> issue you mentioned above.
> 
> The issue I mentioned fails open, so we should fix it but it doesn't
> block anything. Yes, you need to invoke bindep with a test profile,

You're right, we would install more than needed...

> for test builds.

Double checking whether my understanding of the documents is correct:

Let's say our file has two dependencies, one runtime and one test, we
would write this as:
~~
runtime-dep
test-dep [test]
~~

And then invoke "bindep test" and that would install both packages, correct?

In that case our three steps here would be:
* Mark in the reviews some of the dependencies as [test]
* Invoke "bindep test" instead of "bindep" in infra scripts
* Fix the bug (not a blocking issue)

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] binary package install - plan of attack

[Robert Collins]

On 9 May 2016 at 20:43, Andreas Jaeger  wrote:
> On 2016-05-09 10:29, Robert Collins wrote:
>> On 30 April 2016 at 09:00, Andreas Jaeger  wrote:
>>> Paul and myself discussed this morning how to move forward with binary
>>> package installation - the bindep-fallback.txt/other-requirements.txt story.
>>>
>>> I wrote up what we discussed and hope I didn't forgot anything here. Please
>>> review and comment - and sign up if you want to help.
>>>
>>> Andreas - who will board his plane to Washington in a few minutes
>>>
>>> Goals:
>>> 1. bindep-fallback.txt should be minimal and handle packages that the
>>>majority of projects need.
>>> 2. Projects can use other-requirements to document their binary
>>>requirements.
>>> 3. There are no apt-get/yum install commands in jenkins/jobs/
>>>
>>> Proposal:
>>>
>>> 1. Resolve with lifeless how the other-requirements.txt file should
>>>look like, see:
>>>nova: https://review.openstack.org/#/c/200672/
>>>swift: https://review.openstack.org/#/c/298313/
>>
>> I'm not sure what resolving is needed? the only outstanding question I
>
> With resolving I meant: Figure out how the entries should look like and
> whether we need to invoke bindep differently - and whether bindep needs
> a fix.
>
>> saw there was whether the default profile was always active - it is.
>>
>> The issue I mention with bindep is that
>>
>> foo[platform:dpkg test]
>>
>> Will default on on dpkg platforms, because one of the profiles is
>> active - but it shouldn't, because there are other user profiles
>> listed. The rule should be 'A thing is in the default profile if all
>> the profiles listed are automatic profiles, otherwise it is not in the
>> default profile'.
>
> So, how should we write the files?

Testing only dependencies should be in the test profile.

We may want to have a source or similar named profile for
building-from-source of things, but I'd start with just the default
profile for the always-needed deps and test for CI test run
dependencies.

> Should they have [test] for everything in it? In that case, we would
> need to invoke the test profile in bindep and fix bindep to handle the
> issue you mentioned above.

The issue I mentioned fails open, so we should fix it but it doesn't
block anything. Yes, you need to invoke bindep with a test profile,
for test builds.

-Rob

-- 
Robert Collins 
Distinguished Technologist
HP Converged Cloud

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] binary package install - plan of attack

[Andreas Jaeger]

On 2016-05-09 10:29, Robert Collins wrote:
> On 30 April 2016 at 09:00, Andreas Jaeger  wrote:
>> Paul and myself discussed this morning how to move forward with binary
>> package installation - the bindep-fallback.txt/other-requirements.txt story.
>>
>> I wrote up what we discussed and hope I didn't forgot anything here. Please
>> review and comment - and sign up if you want to help.
>>
>> Andreas - who will board his plane to Washington in a few minutes
>>
>> Goals:
>> 1. bindep-fallback.txt should be minimal and handle packages that the
>>majority of projects need.
>> 2. Projects can use other-requirements to document their binary
>>requirements.
>> 3. There are no apt-get/yum install commands in jenkins/jobs/
>>
>> Proposal:
>>
>> 1. Resolve with lifeless how the other-requirements.txt file should
>>look like, see:
>>nova: https://review.openstack.org/#/c/200672/
>>swift: https://review.openstack.org/#/c/298313/
> 
> I'm not sure what resolving is needed? the only outstanding question I

With resolving I meant: Figure out how the entries should look like and
whether we need to invoke bindep differently - and whether bindep needs
a fix.

> saw there was whether the default profile was always active - it is.
> 
> The issue I mention with bindep is that
> 
> foo[platform:dpkg test]
> 
> Will default on on dpkg platforms, because one of the profiles is
> active - but it shouldn't, because there are other user profiles
> listed. The rule should be 'A thing is in the default profile if all
> the profiles listed are automatic profiles, otherwise it is not in the
> default profile'.

So, how should we write the files?

Should they have [test] for everything in it? In that case, we would
need to invoke the test profile in bindep and fix bindep to handle the
issue you mentioned above.

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] binary package install - plan of attack

[Robert Collins]

On 30 April 2016 at 09:00, Andreas Jaeger  wrote:
> Paul and myself discussed this morning how to move forward with binary
> package installation - the bindep-fallback.txt/other-requirements.txt story.
>
> I wrote up what we discussed and hope I didn't forgot anything here. Please
> review and comment - and sign up if you want to help.
>
> Andreas - who will board his plane to Washington in a few minutes
>
> Goals:
> 1. bindep-fallback.txt should be minimal and handle packages that the
>majority of projects need.
> 2. Projects can use other-requirements to document their binary
>requirements.
> 3. There are no apt-get/yum install commands in jenkins/jobs/
>
> Proposal:
>
> 1. Resolve with lifeless how the other-requirements.txt file should
>look like, see:
>nova: https://review.openstack.org/#/c/200672/
>swift: https://review.openstack.org/#/c/298313/

I'm not sure what resolving is needed? the only outstanding question I
saw there was whether the default profile was always active - it is.

The issue I mention with bindep is that

foo[platform:dpkg test]

Will default on on dpkg platforms, because one of the profiles is
active - but it shouldn't, because there are other user profiles
listed. The rule should be 'A thing is in the default profile if all
the profiles listed are automatic profiles, otherwise it is not in the
default profile'.

-Rob


-- 
Robert Collins 
Distinguished Technologist
HP Converged Cloud

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra