Nod, it is the right time to ask for this. Regards
2016-03-22 20:07 GMT+01:00 Paul Belanger <pabelan...@redhat.com>: > On Tue, Mar 22, 2016 at 11:45:12AM -0700, Colleen Murphy wrote: > > On Mon, Mar 21, 2016 at 10:17 AM, Colleen Murphy <coll...@gazlene.net> > > wrote: > > > > > On Thu, Mar 17, 2016 at 11:48 AM, Colleen Murphy <coll...@gazlene.net> > > > wrote: > > > > > >> The networking team at HPE received our request and would like to > have a > > >> call next week to review it. Our liaison, Venu, should have a draft > network > > >> diagram we can review. Who would like to join, and what times/days > work > > >> best? I would propose Tuesday at 1800 UTC (one hour before the Infra > > >> meeting). > > >> > > >> Colleen > > >> > > > A call has been scheduled for 1800-1845 UTC on Tuesday, March 22. > > > Invitations were sent out to folks who expressed interest in attending > and > > > I can share the meeting phone number and conference ID with anyone who > was > > > missed. > > > > > > Allison brought up using the asterisk server for the call and it was > not > > > responded to - I suspect either they didn't understand or didn't feel > > > comfortable with it. It would be my preference to not push the issue, > as > > > they are extending the invitation to us, not the other way around. > Instead > > > I can commit to taking and dispersing detailed notes. > > > > > > Colleen > > > > > Notes from today's meeting: > > > > 1) 1G or 10G? > > - 10G useful for image transfers and mirrors in cloud > > - Venu to connect with DC ops ensure 10G > > > > 2) ipv6? > > - Venu to ask verizon to activate /48 block, will take a couple of days > > > > 3) how many vlans? > > - one untagged for pxe/management, one tagged for public > > > I had to drop off after this point, but did we talk about them (HP team) > wiring > up 2 network interfaces, assuming our NICs support it? I know we > currently are > doing everything with a single interface. > > Even if we continue to use the single NIC, asking to have the 2nd wired > might be > worth it for down the road. > > > 4) keep 10.10.16.0/24 for internal network > > > > 5) Do we need nic bonding? > > - no > > > > 6) Any load balancing requirement? > > - no > > - if we were to add load balancing we would host it ourselves > > > > 5) Access requirements? > > - full inbound/outbound internet access - no ports blocked > > - firewalls managed locally > > > > The network diagram will need to have some parts redacted before we can > > share it publicly. > > > > Colleen > > > _______________________________________________ > > OpenStack-Infra mailing list > > OpenStack-Infra@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >
_______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
