September 2013 - Release-team - mailman3.cels.anl.gov

Re: [Release-team] [Sysadmins] running a minor release this week.
by Land, Miriam L. 24 Sep '13

24 Sep '13

Looks great to me. I had the spreadsheet open when you renamed and it just changed the title at the top. Everything was fine. Miriam On 9/24/13 11:32 AM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >Miriam, take a look at what I'm doing in the deploy column, let me know >if this is what you want. > >Remember, I renamed the new spread sheet to KBase Services. The KBase >Service II spreadsheet no longer exists. > > >On Sep 24, 2013, at 9:33 AM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > >> Let's see how it works in practice. >> >> Thanks Miriam, Shane. >> >> Tom >> >> >> On Sep 24, 2013, at 8:40 AM, Shane Canon <scanon(a)lbl.gov> wrote: >> >>> >>> I like this approach (i.e. <state><attempt>/<person>) since it cuts >>>back on column bloat. Even for a mini-build >>> I think it is useful. >>> >>> --Shane >>> >>> >>> On Sep 24, 2013, at 5:02 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >>> >>>> To be clear, I haven't always been in full compliance with my own >>>>request. >>>> Rather than doubling the number of columns in the spreadsheet, I was >>>> hoping that we could provide a little more information in the column >>>>we >>>> currently use. >>>> >>>> Steve Moulton started using failed/steve, passed2/steve, >>>>passed3/steve for >>>> a series of deploys and redeploys. It was very helpful. If I had >>>>been >>>> consistent on using passed/miriam, passed2/miriam, passed3/miriam, >>>>then it >>>> would be clearer which version was tested and ready. >>>> >>>> This may be an undo burden for a mini build where we have a limit of >>>>one >>>> deploy and one redeploy. In addition we use separate columns for each >>>> stage. I had a selfish interest in improving communication and >>>>developing >>>> habits that would help me in future builds. >>>> >>>> I am willing to withdraw my request if it seems unreasonable for the >>>> current build. >>>> >>>> Miriam >>>> >>>> >>>> On 9/23/13 3:38 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>> >>>>> Can you add what you need? >>>>> >>>>> Thanks. >>>>> >>>>> Tom >>>>> >>>>> >>>>> On Sep 23, 2013, at 2:37 PM, "Land, Miriam L." <landml(a)ornl.gov> >>>>>wrote: >>>>> >>>>>> It would help me out if a name or initials plus a date/version were >>>>>> included in the spreadsheet when deployment and testing were done. >>>>>>It >>>>>> will help me communicate with the right person and help keep track >>>>>>of >>>>>> which version is being tested. After the last build, I wasn't sure >>>>>>if >>>>>> anything was deployed after I left and was untested. >>>>>> >>>>>> Thanks. >>>>>> >>>>>> Miriam >>>>>> >>>>>> On 9/23/13 1:44 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>>>> >>>>>>> OK. Let me look at both shock and awe service. Dantong >>>>>>> >>>>>>> >>>>>>> On 9/23/13 1:42 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>>>> >>>>>>>> Dantong, >>>>>>>> >>>>>>>> Can you look into something else? Shock service or awe service? >>>>>>>> >>>>>>>> Tom >>>>>>>> >>>>>>>> >>>>>>>> On Sep 23, 2013, at 12:39 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>>>>>> >>>>>>>>> I will build m5nr today. Thanks Dantong >>>>>>>>> >>>>>>>>> On 9/23/13 12:40 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> >>>>>>>>>wrote: >>>>>>>>> >>>>>>>>>> We need to regroup the team. There are a number of items that >>>>>>>>>>are >>>>>>>>>> lingering. >>>>>>>>>> >>>>>>>>>> 1) The last build, we need to get the ubuntu image posted. To do >>>>>>>>>> this >>>>>>>>>> we >>>>>>>>>> need some indication from Miriam that it's been adequately >>>>>>>>>>tested. >>>>>>>>>> We >>>>>>>>>> need Tom or Neal to modify the kbase.us download site to point >>>>>>>>>>at >>>>>>>>>> it. >>>>>>>>>> >>>>>>>>>> 2) We need to agree to get the mac dmg out the door, or say >>>>>>>>>>we're >>>>>>>>>> not >>>>>>>>>> going to get it done. >>>>>>>>>> >>>>>>>>>> 3) we need to start running mini-builds. We're already totally >>>>>>>>>> missed >>>>>>>>>> two >>>>>>>>>> weeks. I'd like to start one today. We have the following >>>>>>>>>> >>>>>>>>>> m5nr >>>>>>>>>> communities_api >>>>>>>>>> invocation_service >>>>>>>>>> shock_service >>>>>>>>>> awe_service >>>>>>>>>> >>>>>>>>>> The latter two are just installers, but should be tested in the >>>>>>>>>>test >>>>>>>>>> environment. >>>>>>>>>> >>>>>>>>>> 4) we need someone to act as the primary coordinator of these >>>>>>>>>>minor >>>>>>>>>> releases. >>>>>>>>>> >>>>>>>>>> Please advise me of your availability and willingness to work on >>>>>>>>>> releases >>>>>>>>>> this this week and each following week until the SAC. >>>>>>>>>> >>>>>>>>>> Tom >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Release-team mailing list >>>>>>>>>> Release-team(a)lists.kbase.us >>>>>>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Release-team mailing list >>>>>>> Release-team(a)lists.kbase.us >>>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> sysadmins mailing list >>>> sysadmins(a)lists.kbase.us >>>> https://lists.kbase.us/mailman/listinfo/sysadmins >>> >> >

1 0

Re: [Release-team] [Sysadmins] running a minor release this week.
by Thomas Brettin 24 Sep '13

24 Sep '13

Miriam, take a look at what I'm doing in the deploy column, let me know if this is what you want. Remember, I renamed the new spread sheet to KBase Services. The KBase Service II spreadsheet no longer exists. On Sep 24, 2013, at 9:33 AM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > Let's see how it works in practice. > > Thanks Miriam, Shane. > > Tom > > > On Sep 24, 2013, at 8:40 AM, Shane Canon <scanon(a)lbl.gov> wrote: > >> >> I like this approach (i.e. <state><attempt>/<person>) since it cuts back on column bloat. Even for a mini-build >> I think it is useful. >> >> --Shane >> >> >> On Sep 24, 2013, at 5:02 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >> >>> To be clear, I haven't always been in full compliance with my own request. >>> Rather than doubling the number of columns in the spreadsheet, I was >>> hoping that we could provide a little more information in the column we >>> currently use. >>> >>> Steve Moulton started using failed/steve, passed2/steve, passed3/steve for >>> a series of deploys and redeploys. It was very helpful. If I had been >>> consistent on using passed/miriam, passed2/miriam, passed3/miriam, then it >>> would be clearer which version was tested and ready. >>> >>> This may be an undo burden for a mini build where we have a limit of one >>> deploy and one redeploy. In addition we use separate columns for each >>> stage. I had a selfish interest in improving communication and developing >>> habits that would help me in future builds. >>> >>> I am willing to withdraw my request if it seems unreasonable for the >>> current build. >>> >>> Miriam >>> >>> >>> On 9/23/13 3:38 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>> >>>> Can you add what you need? >>>> >>>> Thanks. >>>> >>>> Tom >>>> >>>> >>>> On Sep 23, 2013, at 2:37 PM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >>>> >>>>> It would help me out if a name or initials plus a date/version were >>>>> included in the spreadsheet when deployment and testing were done. It >>>>> will help me communicate with the right person and help keep track of >>>>> which version is being tested. After the last build, I wasn't sure if >>>>> anything was deployed after I left and was untested. >>>>> >>>>> Thanks. >>>>> >>>>> Miriam >>>>> >>>>> On 9/23/13 1:44 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>>> >>>>>> OK. Let me look at both shock and awe service. Dantong >>>>>> >>>>>> >>>>>> On 9/23/13 1:42 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>>> >>>>>>> Dantong, >>>>>>> >>>>>>> Can you look into something else? Shock service or awe service? >>>>>>> >>>>>>> Tom >>>>>>> >>>>>>> >>>>>>> On Sep 23, 2013, at 12:39 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>>>>> >>>>>>>> I will build m5nr today. Thanks Dantong >>>>>>>> >>>>>>>> On 9/23/13 12:40 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>>>>> >>>>>>>>> We need to regroup the team. There are a number of items that are >>>>>>>>> lingering. >>>>>>>>> >>>>>>>>> 1) The last build, we need to get the ubuntu image posted. To do >>>>>>>>> this >>>>>>>>> we >>>>>>>>> need some indication from Miriam that it's been adequately tested. >>>>>>>>> We >>>>>>>>> need Tom or Neal to modify the kbase.us download site to point at >>>>>>>>> it. >>>>>>>>> >>>>>>>>> 2) We need to agree to get the mac dmg out the door, or say we're >>>>>>>>> not >>>>>>>>> going to get it done. >>>>>>>>> >>>>>>>>> 3) we need to start running mini-builds. We're already totally >>>>>>>>> missed >>>>>>>>> two >>>>>>>>> weeks. I'd like to start one today. We have the following >>>>>>>>> >>>>>>>>> m5nr >>>>>>>>> communities_api >>>>>>>>> invocation_service >>>>>>>>> shock_service >>>>>>>>> awe_service >>>>>>>>> >>>>>>>>> The latter two are just installers, but should be tested in the test >>>>>>>>> environment. >>>>>>>>> >>>>>>>>> 4) we need someone to act as the primary coordinator of these minor >>>>>>>>> releases. >>>>>>>>> >>>>>>>>> Please advise me of your availability and willingness to work on >>>>>>>>> releases >>>>>>>>> this this week and each following week until the SAC. >>>>>>>>> >>>>>>>>> Tom >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Release-team mailing list >>>>>>>>> Release-team(a)lists.kbase.us >>>>>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Release-team mailing list >>>>>> Release-team(a)lists.kbase.us >>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>> >>>> >>> >>> _______________________________________________ >>> sysadmins mailing list >>> sysadmins(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/sysadmins >> >

1 0

Re: [Release-team] [Sysadmins] Deployment this week
by Yu, Dantong 24 Sep '13

24 Sep '13

You can start test shock. But not awe. I changed the entry and added my name. Dantong On 9/24/13 10:38 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >I'm having a problem interpreting the comments left in the deployment >column of the new KBase Services spreadsheet. > https://docs.google.com/spreadsheet/ccc?key=0AriSbOyynCz1dDdJRHJBcGszaldl >U >E5KaG5yNHBRcWc > >The history shows that an anonymous user added the deployment remarks. Are >the shock_service, awe_service, and invocation ready to test? > >Miriam > >_______________________________________________ >sysadmins mailing list >sysadmins(a)lists.kbase.us >https://lists.kbase.us/mailman/listinfo/sysadmins

1 0

Re: [Release-team] Deployment this week
by Thomas Brettin 24 Sep '13

24 Sep '13

Miriam, Please see my previous email. Close the spreadsheet, search for KBase Services, and you should be good to go. Tom On Sep 24, 2013, at 9:38 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > I'm having a problem interpreting the comments left in the deployment > column of the new KBase Services spreadsheet. > https://docs.google.com/spreadsheet/ccc?key=0AriSbOyynCz1dDdJRHJBcGszaldlU > E5KaG5yNHBRcWc > > The history shows that an anonymous user added the deployment remarks. Are > the shock_service, awe_service, and invocation ready to test? > > Miriam >

1 0

Deployment this week
by Land, Miriam L. 24 Sep '13

24 Sep '13

I'm having a problem interpreting the comments left in the deployment column of the new KBase Services spreadsheet. https://docs.google.com/spreadsheet/ccc?key=0AriSbOyynCz1dDdJRHJBcGszaldlU E5KaG5yNHBRcWc The history shows that an anonymous user added the deployment remarks. Are the shock_service, awe_service, and invocation ready to test? Miriam

1 0

KBase Services spread sheet
by Thomas Brettin 24 Sep '13

24 Sep '13

As per a request, I've renamed the two spread sheets. The original KBase Services has been renamed to KBase Services Year 1 The new KBase Services II has been renamed to KBase Services As we need to pull things forward from the Year 1 workbook, lets to so, but not until it is needed. This way, we know it's essential. Best, Tom On Sep 24, 2013, at 9:33 AM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > Let's see how it works in practice. > > Thanks Miriam, Shane. > > Tom > > > On Sep 24, 2013, at 8:40 AM, Shane Canon <scanon(a)lbl.gov> wrote: > >> >> I like this approach (i.e. <state><attempt>/<person>) since it cuts back on column bloat. Even for a mini-build >> I think it is useful. >> >> --Shane >> >> >> On Sep 24, 2013, at 5:02 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >> >>> To be clear, I haven't always been in full compliance with my own request. >>> Rather than doubling the number of columns in the spreadsheet, I was >>> hoping that we could provide a little more information in the column we >>> currently use. >>> >>> Steve Moulton started using failed/steve, passed2/steve, passed3/steve for >>> a series of deploys and redeploys. It was very helpful. If I had been >>> consistent on using passed/miriam, passed2/miriam, passed3/miriam, then it >>> would be clearer which version was tested and ready. >>> >>> This may be an undo burden for a mini build where we have a limit of one >>> deploy and one redeploy. In addition we use separate columns for each >>> stage. I had a selfish interest in improving communication and developing >>> habits that would help me in future builds. >>> >>> I am willing to withdraw my request if it seems unreasonable for the >>> current build. >>> >>> Miriam >>> >>> >>> On 9/23/13 3:38 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>> >>>> Can you add what you need? >>>> >>>> Thanks. >>>> >>>> Tom >>>> >>>> >>>> On Sep 23, 2013, at 2:37 PM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >>>> >>>>> It would help me out if a name or initials plus a date/version were >>>>> included in the spreadsheet when deployment and testing were done. It >>>>> will help me communicate with the right person and help keep track of >>>>> which version is being tested. After the last build, I wasn't sure if >>>>> anything was deployed after I left and was untested. >>>>> >>>>> Thanks. >>>>> >>>>> Miriam >>>>> >>>>> On 9/23/13 1:44 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>>> >>>>>> OK. Let me look at both shock and awe service. Dantong >>>>>> >>>>>> >>>>>> On 9/23/13 1:42 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>>> >>>>>>> Dantong, >>>>>>> >>>>>>> Can you look into something else? Shock service or awe service? >>>>>>> >>>>>>> Tom >>>>>>> >>>>>>> >>>>>>> On Sep 23, 2013, at 12:39 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>>>>> >>>>>>>> I will build m5nr today. Thanks Dantong >>>>>>>> >>>>>>>> On 9/23/13 12:40 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>>>>> >>>>>>>>> We need to regroup the team. There are a number of items that are >>>>>>>>> lingering. >>>>>>>>> >>>>>>>>> 1) The last build, we need to get the ubuntu image posted. To do >>>>>>>>> this >>>>>>>>> we >>>>>>>>> need some indication from Miriam that it's been adequately tested. >>>>>>>>> We >>>>>>>>> need Tom or Neal to modify the kbase.us download site to point at >>>>>>>>> it. >>>>>>>>> >>>>>>>>> 2) We need to agree to get the mac dmg out the door, or say we're >>>>>>>>> not >>>>>>>>> going to get it done. >>>>>>>>> >>>>>>>>> 3) we need to start running mini-builds. We're already totally >>>>>>>>> missed >>>>>>>>> two >>>>>>>>> weeks. I'd like to start one today. We have the following >>>>>>>>> >>>>>>>>> m5nr >>>>>>>>> communities_api >>>>>>>>> invocation_service >>>>>>>>> shock_service >>>>>>>>> awe_service >>>>>>>>> >>>>>>>>> The latter two are just installers, but should be tested in the test >>>>>>>>> environment. >>>>>>>>> >>>>>>>>> 4) we need someone to act as the primary coordinator of these minor >>>>>>>>> releases. >>>>>>>>> >>>>>>>>> Please advise me of your availability and willingness to work on >>>>>>>>> releases >>>>>>>>> this this week and each following week until the SAC. >>>>>>>>> >>>>>>>>> Tom >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Release-team mailing list >>>>>>>>> Release-team(a)lists.kbase.us >>>>>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Release-team mailing list >>>>>> Release-team(a)lists.kbase.us >>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>> >>>> >>> >>> _______________________________________________ >>> sysadmins mailing list >>> sysadmins(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/sysadmins >> >

1 0

Re: [Release-team] [Sysadmins] running a minor release this week.
by Thomas Brettin 24 Sep '13

24 Sep '13

Let's see how it works in practice. Thanks Miriam, Shane. Tom On Sep 24, 2013, at 8:40 AM, Shane Canon <scanon(a)lbl.gov> wrote: > > I like this approach (i.e. <state><attempt>/<person>) since it cuts back on column bloat. Even for a mini-build > I think it is useful. > > --Shane > > > On Sep 24, 2013, at 5:02 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > >> To be clear, I haven't always been in full compliance with my own request. >> Rather than doubling the number of columns in the spreadsheet, I was >> hoping that we could provide a little more information in the column we >> currently use. >> >> Steve Moulton started using failed/steve, passed2/steve, passed3/steve for >> a series of deploys and redeploys. It was very helpful. If I had been >> consistent on using passed/miriam, passed2/miriam, passed3/miriam, then it >> would be clearer which version was tested and ready. >> >> This may be an undo burden for a mini build where we have a limit of one >> deploy and one redeploy. In addition we use separate columns for each >> stage. I had a selfish interest in improving communication and developing >> habits that would help me in future builds. >> >> I am willing to withdraw my request if it seems unreasonable for the >> current build. >> >> Miriam >> >> >> On 9/23/13 3:38 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >> >>> Can you add what you need? >>> >>> Thanks. >>> >>> Tom >>> >>> >>> On Sep 23, 2013, at 2:37 PM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >>> >>>> It would help me out if a name or initials plus a date/version were >>>> included in the spreadsheet when deployment and testing were done. It >>>> will help me communicate with the right person and help keep track of >>>> which version is being tested. After the last build, I wasn't sure if >>>> anything was deployed after I left and was untested. >>>> >>>> Thanks. >>>> >>>> Miriam >>>> >>>> On 9/23/13 1:44 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>> >>>>> OK. Let me look at both shock and awe service. Dantong >>>>> >>>>> >>>>> On 9/23/13 1:42 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>> >>>>>> Dantong, >>>>>> >>>>>> Can you look into something else? Shock service or awe service? >>>>>> >>>>>> Tom >>>>>> >>>>>> >>>>>> On Sep 23, 2013, at 12:39 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>>>> >>>>>>> I will build m5nr today. Thanks Dantong >>>>>>> >>>>>>> On 9/23/13 12:40 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>>>> >>>>>>>> We need to regroup the team. There are a number of items that are >>>>>>>> lingering. >>>>>>>> >>>>>>>> 1) The last build, we need to get the ubuntu image posted. To do >>>>>>>> this >>>>>>>> we >>>>>>>> need some indication from Miriam that it's been adequately tested. >>>>>>>> We >>>>>>>> need Tom or Neal to modify the kbase.us download site to point at >>>>>>>> it. >>>>>>>> >>>>>>>> 2) We need to agree to get the mac dmg out the door, or say we're >>>>>>>> not >>>>>>>> going to get it done. >>>>>>>> >>>>>>>> 3) we need to start running mini-builds. We're already totally >>>>>>>> missed >>>>>>>> two >>>>>>>> weeks. I'd like to start one today. We have the following >>>>>>>> >>>>>>>> m5nr >>>>>>>> communities_api >>>>>>>> invocation_service >>>>>>>> shock_service >>>>>>>> awe_service >>>>>>>> >>>>>>>> The latter two are just installers, but should be tested in the test >>>>>>>> environment. >>>>>>>> >>>>>>>> 4) we need someone to act as the primary coordinator of these minor >>>>>>>> releases. >>>>>>>> >>>>>>>> Please advise me of your availability and willingness to work on >>>>>>>> releases >>>>>>>> this this week and each following week until the SAC. >>>>>>>> >>>>>>>> Tom >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Release-team mailing list >>>>>>>> Release-team(a)lists.kbase.us >>>>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Release-team mailing list >>>>> Release-team(a)lists.kbase.us >>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>> >>> >> >> _______________________________________________ >> sysadmins mailing list >> sysadmins(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/sysadmins >

1 0

Re: [Release-team] [Sysadmins] running a minor release this week.
by Shane Canon 24 Sep '13

24 Sep '13

I like this approach (i.e. <state><attempt>/<person>) since it cuts back on column bloat. Even for a mini-build I think it is useful. --Shane On Sep 24, 2013, at 5:02 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > To be clear, I haven't always been in full compliance with my own request. > Rather than doubling the number of columns in the spreadsheet, I was > hoping that we could provide a little more information in the column we > currently use. > > Steve Moulton started using failed/steve, passed2/steve, passed3/steve for > a series of deploys and redeploys. It was very helpful. If I had been > consistent on using passed/miriam, passed2/miriam, passed3/miriam, then it > would be clearer which version was tested and ready. > > This may be an undo burden for a mini build where we have a limit of one > deploy and one redeploy. In addition we use separate columns for each > stage. I had a selfish interest in improving communication and developing > habits that would help me in future builds. > > I am willing to withdraw my request if it seems unreasonable for the > current build. > > Miriam > > > On 9/23/13 3:38 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: > >> Can you add what you need? >> >> Thanks. >> >> Tom >> >> >> On Sep 23, 2013, at 2:37 PM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >> >>> It would help me out if a name or initials plus a date/version were >>> included in the spreadsheet when deployment and testing were done. It >>> will help me communicate with the right person and help keep track of >>> which version is being tested. After the last build, I wasn't sure if >>> anything was deployed after I left and was untested. >>> >>> Thanks. >>> >>> Miriam >>> >>> On 9/23/13 1:44 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>> >>>> OK. Let me look at both shock and awe service. Dantong >>>> >>>> >>>> On 9/23/13 1:42 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>> >>>>> Dantong, >>>>> >>>>> Can you look into something else? Shock service or awe service? >>>>> >>>>> Tom >>>>> >>>>> >>>>> On Sep 23, 2013, at 12:39 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>>> >>>>>> I will build m5nr today. Thanks Dantong >>>>>> >>>>>> On 9/23/13 12:40 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>>> >>>>>>> We need to regroup the team. There are a number of items that are >>>>>>> lingering. >>>>>>> >>>>>>> 1) The last build, we need to get the ubuntu image posted. To do >>>>>>> this >>>>>>> we >>>>>>> need some indication from Miriam that it's been adequately tested. >>>>>>> We >>>>>>> need Tom or Neal to modify the kbase.us download site to point at >>>>>>> it. >>>>>>> >>>>>>> 2) We need to agree to get the mac dmg out the door, or say we're >>>>>>> not >>>>>>> going to get it done. >>>>>>> >>>>>>> 3) we need to start running mini-builds. We're already totally >>>>>>> missed >>>>>>> two >>>>>>> weeks. I'd like to start one today. We have the following >>>>>>> >>>>>>> m5nr >>>>>>> communities_api >>>>>>> invocation_service >>>>>>> shock_service >>>>>>> awe_service >>>>>>> >>>>>>> The latter two are just installers, but should be tested in the test >>>>>>> environment. >>>>>>> >>>>>>> 4) we need someone to act as the primary coordinator of these minor >>>>>>> releases. >>>>>>> >>>>>>> Please advise me of your availability and willingness to work on >>>>>>> releases >>>>>>> this this week and each following week until the SAC. >>>>>>> >>>>>>> Tom >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Release-team mailing list >>>>>>> Release-team(a)lists.kbase.us >>>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Release-team mailing list >>>> Release-team(a)lists.kbase.us >>>> https://lists.kbase.us/mailman/listinfo/release-team >>> >> > > _______________________________________________ > sysadmins mailing list > sysadmins(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/sysadmins

1 0

Re: [Release-team] running a minor release this week.
by Land, Miriam L. 24 Sep '13

24 Sep '13

To be clear, I haven't always been in full compliance with my own request. Rather than doubling the number of columns in the spreadsheet, I was hoping that we could provide a little more information in the column we currently use. Steve Moulton started using failed/steve, passed2/steve, passed3/steve for a series of deploys and redeploys. It was very helpful. If I had been consistent on using passed/miriam, passed2/miriam, passed3/miriam, then it would be clearer which version was tested and ready. This may be an undo burden for a mini build where we have a limit of one deploy and one redeploy. In addition we use separate columns for each stage. I had a selfish interest in improving communication and developing habits that would help me in future builds. I am willing to withdraw my request if it seems unreasonable for the current build. Miriam On 9/23/13 3:38 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >Can you add what you need? > >Thanks. > >Tom > > >On Sep 23, 2013, at 2:37 PM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > >> It would help me out if a name or initials plus a date/version were >> included in the spreadsheet when deployment and testing were done. It >> will help me communicate with the right person and help keep track of >> which version is being tested. After the last build, I wasn't sure if >> anything was deployed after I left and was untested. >> >> Thanks. >> >> Miriam >> >> On 9/23/13 1:44 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >> >>> OK. Let me look at both shock and awe service. Dantong >>> >>> >>> On 9/23/13 1:42 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>> >>>> Dantong, >>>> >>>> Can you look into something else? Shock service or awe service? >>>> >>>> Tom >>>> >>>> >>>> On Sep 23, 2013, at 12:39 PM, "Yu, Dantong" <dtyu(a)bnl.gov> wrote: >>>> >>>>> I will build m5nr today. Thanks Dantong >>>>> >>>>> On 9/23/13 12:40 PM, "Thomas Brettin" <brettin(a)mcs.anl.gov> wrote: >>>>> >>>>>> We need to regroup the team. There are a number of items that are >>>>>> lingering. >>>>>> >>>>>> 1) The last build, we need to get the ubuntu image posted. To do >>>>>>this >>>>>> we >>>>>> need some indication from Miriam that it's been adequately tested. >>>>>>We >>>>>> need Tom or Neal to modify the kbase.us download site to point at >>>>>>it. >>>>>> >>>>>> 2) We need to agree to get the mac dmg out the door, or say we're >>>>>>not >>>>>> going to get it done. >>>>>> >>>>>> 3) we need to start running mini-builds. We're already totally >>>>>>missed >>>>>> two >>>>>> weeks. I'd like to start one today. We have the following >>>>>> >>>>>> m5nr >>>>>> communities_api >>>>>> invocation_service >>>>>> shock_service >>>>>> awe_service >>>>>> >>>>>> The latter two are just installers, but should be tested in the test >>>>>> environment. >>>>>> >>>>>> 4) we need someone to act as the primary coordinator of these minor >>>>>> releases. >>>>>> >>>>>> Please advise me of your availability and willingness to work on >>>>>> releases >>>>>> this this week and each following week until the SAC. >>>>>> >>>>>> Tom >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Release-team mailing list >>>>>> Release-team(a)lists.kbase.us >>>>>> https://lists.kbase.us/mailman/listinfo/release-team >>>>> >>>> >>> >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/release-team >> >

1 0

Re: [Release-team] m5nr deployed
by Dan Olson 23 Sep '13

23 Sep '13

Use deploy.vm from now on. I'm not sure that deploy.rsc was the problem here though. --Dan > On Sep 23, 2013, at 1:53 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > > There were a few bumps. The first was the deploy.rsc command didn't seem to work properly, that is no scripts from the m5nr module were found in deployment/bin, and there were not any errors in the output of deploy.rsc. > > One note on the deploy.rsc, the kbrest_common is a new module. It is purely a support library. It is very similar in it's role as kbapi_common. It doesn't have a tag yet, and so deploy.rsc pulled master and put this message to output > > kbrest_common didn't have a tag > * Using for kbrest_common > > Anyways, I fell back to the manual deploy. It worked fine, but there were a couple items. > > had to install solr > from m5nr directory, make > > had to start solr > /etc/init.d/solr start > > had to start apache > apachectl start > > root@test-m5nr:~# source /kb/deployment/user-env.sh > root@test-m5nr:~# m5nr-get-sources > {"version":"9","url":"http://localhost:7103/api.cgi/m5nr/sources","data":[]} > > > Overall, it took about 10 mins to build. > > Miriam, it's ready for you. The requisite servers (solr and apache) are running. > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0