13:29:15 <dmcbride> #startmeeting OPNFV Danube 3 release daily
13:29:15 <collabot`> Meeting started Thu Jun  1 13:29:15 2017 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:29:15 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:29:15 <collabot`> The meeting name has been set to 'opnfv_danube_3_release_daily'
13:29:45 <dmcbride> #topic roll call
13:29:56 <dmcbride> #info David McBride
13:30:50 <dmcbride> #topic release schedule
13:31:21 <dmcbride> #info release is 1 week from today (June 8)
13:31:47 <dmcbride> #info June 6 ==> finish testing
13:32:12 <dmcbride> #info June 7 ==> finish documentation / JIRA cleanup
13:32:52 <dmcbride> #info June 8 ==> repo tagging / artifacts
13:33:08 <mbeierl> #info Mark Beierl
13:33:39 <mbeierl> Just a heads up... there are a few Intel pods that need network reconfiguration.  This may have an impact on the release date for 3.0
13:34:27 <georgk> #info Georg Kunz
13:35:02 <mbeierl> The latest from jmorgan1 is that the downtime should be a couple days, but still, we should be prepared for possible delays
13:35:44 <dmcbride> #info mbeierl notes that there are a few Intel pods that need network reconfiguration.  This may have an impact on the release date for 3.0
13:36:06 <dmcbride> #info The latest from jmorgan1 is that the downtime should be a couple days, but still, we should be prepared for possible delays
13:36:53 <dmcbride> mbeierl: Jack brought that up at the release meeting two days ago, but I haven't heard anything since
13:37:20 <jmorgan1> Storperf might be most impacted as others have a 2nd POd (Apex, Joid, Compass)
13:37:20 <dmcbride> mbeierl: I think that he was going to send an email to the mailing list with details.  Did that happen?
13:37:34 <dmcbride> hey, Jack
13:37:38 <mbeierl> #link https://www.tripit.com/feed/ical/private/A85ACDA5-3EF524C39560F6FD8637A307B4373897/tripit.ics
13:37:40 <jmorgan1> yes, it did
13:37:41 <mbeierl> oops
13:37:44 <mbeierl> wrong link
13:37:53 <mbeierl> #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/attachments/20170531/284ac3a5/attachment.html
13:38:07 <jmorgan1> hey david
13:38:58 <dmcbride> #info link is to email from jmorgan1 to the team regarding the lab downtime
13:42:36 <dmcbride> jmorgan1: I think that you said earlier in the week that there is a list of projects that are affected
13:43:05 <dmcbride> or, that *may* be affected
13:43:16 <jmorgan1> dmcbride: see email link above
13:43:50 <mbeierl> jmorgan1, dmcbride: the link renders HTML as text, so it's not very easy to read online.
13:44:08 <mbeierl> #info the list is CPerf, JOID, Apex, Compass4nfv and StorPerf
13:44:17 <mbeierl> As well as one CI Standalone pod
13:44:23 <jmorgan1> short list is Cperf (POD2), CI standalone (POD4), Joid (POD5), Apex (POD7), Compass (POD8), Storperf (POD9)
13:44:29 <mbeierl> jmorgan1: thanks!
13:44:57 <jmorgan1> np
13:45:09 <mbeierl> I don't anticipate any impact to StorPerf at this time as I am still in gerrit review for my last changes
13:46:14 <jmorgan1> mbeierl: good to hear
13:46:19 <mbeierl> However, I understand that things can change, and that what was hoped to be a quick relocate ends up being derailed.  So, rather than put pressure on Jack and the rest of the Intel team, I would like to have a plan in place to delay if needed
13:47:07 <jmorgan1> mbeierl: there is other Intel team ;)
13:48:50 <mbeierl> And we appreciate your commitments to the community.  That's why I don't want there to appear to be pressure on anyone
13:49:31 <dmcbride> for PODs 5, 7, and 8
13:49:55 <jmorgan1> mbeierl: i'm joking, I do have a few helping me do the move ;)
13:50:00 <dmcbride> are the projects attached to those installers affected, as well?
13:50:17 <mbeierl> #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-June/016491.html
13:50:22 <jmorgan1> it might be good to be ready just in case soemthing happens
13:50:43 <mbeierl> Justin indicated that MeiMei is on leave, but did not raise any concerns about the move and the timing
13:50:59 <mbeierl> #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-June/016491.html
13:51:20 <mbeierl> narindergupta: indicated that a delay would be preferred, so I infer that might mean an impact
13:51:38 <jmorgan1> dmcbride: those projects in 5,7,8 have a 2nd CI POD within OPNFV so shouldn't have too big an impact
13:52:34 <mbeierl> And I don't think jmorgan1 has much of a choice in this.  The move must be done
13:53:31 <mbeierl> Does it make sense to send an email explicitly asking for impact?
13:53:56 <dmcbride> jmorgan1: how long do you expect the change to take?
13:54:40 <mbeierl> #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/attachments/20170531/e310a386/attachment.html
13:54:50 <jmorgan1> dmcbride: two days - a day to move servers and antoher for vpn profile set up, switch configuration, change RMM IP and troubleshoot any issues
13:55:23 <jmorgan1> dmcbride: then POD users need to change IP on hosts, then done
13:55:49 <mbeierl> jmorgan1: IP addresses for all nodes, correct?  We are getting new subnets I believe?
13:56:48 <jmorgan1> mbeierl: yes, take a look at POD15 as an example
13:56:51 <jmorgan1> https://wiki.opnfv.org/display/pharos/Intel+Pod15
13:56:56 <mbeierl> jmorgan1: thanks!
13:57:04 <jmorgan1> IP of 10.10.x.0/24 where x = POD#
13:57:17 <mbeierl> Cool!
13:57:33 <jmorgan1> IP are correct in topology diagrams
13:57:51 <jmorgan1> New POD# are 19-24
13:58:01 <jmorgan1> storperf will be POD24
13:58:26 <jmorgan1> I have create wiki pages on 2nd day
13:58:48 <dmcbride> #info jmorgan1 says two days - a day to move servers and antoher for vpn profile set up, switch configuration, change RMM IP and troubleshoot any issues
13:59:09 <dmcbride> #info then POD users need to change IP on hosts, then done
14:00:05 <mbeierl> #info Re-deployment of the OPNFV Installer is probably needed for the changing of IPs.  This is a 2 hour process for me using Apex, so no real impact.
14:00:50 <jmorgan1> right, I'm not too worried about impact assuming everything works as expected
14:01:38 <dmcbride> jmorgan1: I'm not following you
14:01:50 <jmorgan1> dmcbride: which part?
14:01:58 <dmcbride> jmorgan1: are you saying that projects will not be affected for the entire two days?
14:02:18 <dmcbride> jmorgan1: when you said that you're not too worried about the impact
14:03:19 <jmorgan1> dmcbride: no I'm not saying that there is no impact. I'm saying that the impact to the users of the POD is great - change IP and redeploy (2hrs)
14:03:28 <dmcbride> jmorgan1: from my standpoint, I see that we have  6 - 7 days until release and now we're losing 2 days
14:03:29 <jmorgan1> dmcbride: besides the 2 day downtime
14:03:49 <dmcbride> ok
14:04:56 <jmorgan1> dmcbride: a bigger impact to users would be a reinstall of jump host, reconfiguring Jenkins slave, recreating deploy scripts, redeploying ,etc
14:05:04 <jmorgan1> dmcbride: for example
14:06:34 <dmcbride> so, we're out of time for today
14:06:43 <dmcbride> same time, same place tomorrow
14:06:50 <dmcbride> #endmeeting