[opnfv-tech-discuss] Leaving OPNFV

[Parker Berberian]

Hello all,

Today will be my last day at the UNH Interoperability lab. In my new job I
will be unable to continue to contribute to OPNFV as I have been.

I am vacating my TSC seat effective immediately, and recommend that the TSC
hold an ad-hoc election to fill the vacancy.

I want to sincerely thank this community for the opportunities you have
given me. I never would have expected to be a top 3 contributor[1] or take
positions of leadership on an LFN project before graduating college, but
that is the power of open source. I encourage you all to continue to
engender this kind of open collaboration and cooperation. OPNFV is a
diverse and highly skilled community and I have every confidence that you
will continue to meet the challenges ahead of you.

It has been a pleasure working with all of you, and I would love for our
paths to cross again. My linkedin[2] is below if you would like to stay in
touch.

I am leaving behind a very capable team at the UNH-IOL. You can contact
Sawyer at sberge...@iol.unh.edu or nfv-...@iol.unh.edu for any type of
support you would have previously contacted me for.

[1] https://wiki.opnfv.org/display/DEV/2020+Active+Contributors
[2] https://www.linkedin.com/in/parker-berberian-185ab7186/

Thank you and Goodbye,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#24139): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/24139
Mute This Topic: https://lists.opnfv.org/mt/74052816/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] Stepping down as LaaS PTL

[Parker Berberian]

Thank you all for your kind words.

I have not noticed any other nominations, so I feel comfortable announcing
that Sawyer Bergeron is now the PTL of the Lab as a Service project.
Congratulations and good luck Sawyer!

INFO.yaml file updated here: https://gerrit.opnfv.org/gerrit/c/laas/+/70167

Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu


On Tue, Apr 28, 2020 at 5:12 PM David McBride 
wrote:

> Parker,
>
> Thanks for leading LaaS the past few years.  You accomplished a lot.
> Hopefully, you'll be able to continue to contribute to the project, even as
> you step down as PTL.
>
> David
>
> On Thu, Apr 23, 2020 at 7:50 AM Parker Berberian 
> wrote:
>
>> Hello All,
>>
>> After leading the Lab as a Service effort for nearly three years, I am
>> ready to step down as PTL and let someone new take the reins.
>>
>> I nominate Sawyer Bergeron as the new LaaS PTL. In my opinion, he is the
>> most qualified to lead Lab as a Service.
>>
>> As usual, we will have a two week nomination period and then an election
>>
>>
>> Best,
>>
>> Parker Berberian
>>
>> Lead Developer
>>
>> UNH InterOperability Laboratory
>>
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>
>> pberber...@iol.unh.edu
>>
>> www.iol.unh.edu
>> 
>>
>
>
> --
> *David McBride*
> Release Manager
> Linux Foundation Networking (LFN)
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> IRC: dmcbride
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#24135): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/24135
Mute This Topic: https://lists.opnfv.org/mt/73219483/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Stepping down as LaaS PTL

[Parker Berberian]

Hello All,

After leading the Lab as a Service effort for nearly three years, I am
ready to step down as PTL and let someone new take the reins.

I nominate Sawyer Bergeron as the new LaaS PTL. In my opinion, he is the
most qualified to lead Lab as a Service.

As usual, we will have a two week nomination period and then an election


Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#24109): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/24109
Mute This Topic: https://lists.opnfv.org/mt/73219483/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] #laas Lab as a Service Downtime During Upgrades

[Parker Berberian]

Hi all,

This is all completed. Let me and my team know if you experience any issues.

Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu


On Fri, Feb 21, 2020 at 9:43 AM Parker Berberian via Lists.Opnfv.Org
 wrote:

> Hi all,
>
> Lab as a Service at the IOL will be going down briefly later today for
> some upgrades and maintenance. This will not affect any active bookings you
> may have.
>
> If you request a new booking, or you try to reinstall one of your booked
> machines through the dashboard, it may take a few hours for your request to
> be fulfilled.
>
> I will send out another email when all upgrades are complete. Please reach
> out with any questions or concerns.
>
> Best,
>
> Parker Berberian
>
> Lead Developer
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
>
> pberber...@iol.unh.edu
>
> www.iol.unh.edu
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23953): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23953
Mute This Topic: https://lists.opnfv.org/mt/71451705/21656
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #laas Lab as a Service Downtime During Upgrades

[Parker Berberian]

Hi all,

Lab as a Service at the IOL will be going down briefly later today for some
upgrades and maintenance. This will not affect any active bookings you may
have.

If you request a new booking, or you try to reinstall one of your booked
machines through the dashboard, it may take a few hours for your request to
be fulfilled.

I will send out another email when all upgrades are complete. Please reach
out with any questions or concerns.

Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23952): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23952
Mute This Topic: https://lists.opnfv.org/mt/71451705/21656
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] EasyCLA goes LIVE at 9 a.m. on Feb 12

[Parker Berberian]

Glad to see the system works! Thanks David.

-

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu


On Wed, Feb 12, 2020 at 2:47 PM David McBride 
wrote:

> +Parker Berberian 
>
> ... and Parker becomes the first committer after EasyCLA was enabled.
> Woo-hoo!
>
> On Wed, Feb 12, 2020 at 9:50 AM David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> I've been told by the product team that EasyCLA has been enabled.  Please
>> report any issues that you encounter to support.linuxfoundation.org.
>> However, I'd be interested in hearing from developers about their
>> experiences, good or bad, in interacting with the system when they commit
>> code. Feel free to reply to this thread with your description and
>> thoughts.  Thanks.
>>
>> David
>>
>> On Tue, Feb 11, 2020 at 1:26 PM David McBride <
>> dmcbr...@linuxfoundation.org> wrote:
>>
>>> I should also add that if you are an individual contributor (i.e., you
>>> are not working on OPNFV on behalf of an organization), when you commit
>>> code to the repository, you will be directed to EasyCLA to digitally sign
>>> an authorization form.
>>>
>>> David
>>>
>>> On Tue, Feb 11, 2020 at 11:50 AM David McBride <
>>> dmcbr...@linuxfoundation.org> wrote:
>>>
>>>> Team,
>>>>
>>>> Two weeks ago, the OPNFV TSC approved Feb 12 as the cutover date for
>>>> EasyCLA. That date is tomorrow, beginning at 9 a.m. Pacific Time.
>>>>
>>>> All of the major contributing organizations have now identified CLA
>>>> Managers and those CLA Managers have set up white lists in EasyCLA.
>>>>
>>>> When you commit code, you will be asked once to confirm your
>>>> association with your organization.
>>>>
>>>> If you have any problems, please submit a ticket to
>>>> support.linuxfoundation.org.
>>>>
>>>> David
>>>>
>>>> --
>>>> *David McBride*
>>>> Release Manager
>>>> Linux Foundation Networking (LFN)
>>>> Mobile: +1.805.276.8018
>>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>>> IRC: dmcbride
>>>>
>>>
>>>
>>> --
>>> *David McBride*
>>> Release Manager
>>> Linux Foundation Networking (LFN)
>>> Mobile: +1.805.276.8018
>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>> IRC: dmcbride
>>>
>>
>>
>> --
>> *David McBride*
>> Release Manager
>> Linux Foundation Networking (LFN)
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> IRC: dmcbride
>>
>
>
> --
> *David McBride*
> Release Manager
> Linux Foundation Networking (LFN)
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> IRC: dmcbride
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23938): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23938
Mute This Topic: https://lists.opnfv.org/mt/71176574/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #laas LaaS CNTT Upgrades

[Parker Berberian]

Hello all,

The LaaS project is performing hardware upgrades to move towards CNTT
compliance. This includes upgrading the SSD storage and network interfaces.

We plan to upgrade the machines one at a time as they are available, so as
to not interrupt anyone's active booking. Some interruptions may be
unavoidable, and we will communicate to those who will be affected if we
expect some downtime.

Some interface names and drive paths may change as we swap out hardware,
but there should be no major disruption to user's workflow.

Please feel free to reach out to me or my team with any questions.

Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23910): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23910
Mute This Topic: https://lists.opnfv.org/mt/70977157/21656
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] LaaS Outage

[Parker Berberian]

Hi all,

The problem was a misconfiguration of DNS. Everything should be back to
normal.

We apologize for any inconvenience and we encourage you to reach out to our
team if you have any more problems.

Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu


On Mon, Dec 9, 2019 at 4:03 PM sberge...@iol.unh.edu 
wrote:

> Hi all,
>
> LaaS at the UNH IOL is experiencing an outage at the moment because of an
> infra problem. We're working on getting everything back up but for the time
> being no new bookings can be applied.
>
> Will update once the issue is resolved.
>
> Thanks,
> Sawyer Bergeron,
> LaaS Developer,
> UNH IOL
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#23770):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/23770
> Mute This Topic: https://lists.opnfv.org/mt/67884940/1217375
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> pberber...@iol.unh.edu]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23779): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23779
Mute This Topic: https://lists.opnfv.org/mt/67884940/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Brief LaaS Downtime

[Parker Berberian]

Hello all,

Sorry for the short notice, but we are doing a firewall upgrade at the lab
today. This will mean a brief downtime in the VPN connection to your laas
machines. Email me if you have any questions or issues.

Thank you,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23736): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23736
Mute This Topic: https://lists.opnfv.org/mt/61959357/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] APEX Fraser deployment failed

[Parker Berberian]

Hi Vivek,

Unfortunately, I have had very limited success in deploying old versions of
OPNFV. It is recommended that you stick to the latest version of OPNFV
installers.

That said, we would need to see the contents of the network config file to
help troubleshoot.

Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu


On Thu, Oct 17, 2019 at 8:48 AM Vivekanandan Muthukrishnan <
vmuthukrish...@aarnanetworks.com> wrote:

> Hi Apex Team,
>
> We tried to deploy OPNFV Fraser and it failed with the following error
> message.
>
> I am attaching herewith is the log file archive for your reference. It is
> failing while provisioning overcloud VM. Kindly let me know if you know of
> a workaround to resolve this issue.
>
> Thanks & Regards
> Vivek
>
> *OS Details*
>
> [root@opnfv-fraser-02 ~]# uname -r
> 3.10.0-1062.1.2.el7.x86_64
>
> [root@opnfv-fraser-02 ~]# cat /etc/centos-release
> CentOS Linux release 7.7.1908 (Core)
>
> *OPNFV Deployment command*
>
> nohup opnfv-deploy -v --debug -n /etc/opnfv-apex/network_settings_v6.yaml
> -d /etc/opnfv-apex/os-nosdn-nofeature-noha.yaml &
>
> *OPNFV Deployment log snippet*
>
> overcloud.Controller.0.NetworkDeployment:
>   resource_type: OS::TripleO::SoftwareDeployment
>   physical_resource_id: e54d5970-b789-4e92-9dbb-a0f82c275690
>   status: CREATE_FAILED
>   status_reason: |
> Error: resources.NetworkDeployment: Deployment to server failed:
> deploy_status_code : Deployment exited with non-zero status code: 1
> overcloud.Compute.0.NetworkDeployment:
>   resource_type: OS::TripleO::SoftwareDeployment
>   physical_resource_id: 0c988418-e0e2-4d25-80ee-388bc69ae80c
>   status: CREATE_FAILED
>   status_reason: |
> .
> 2019-10-17 12:25:21Z [overcloud]: CREATE_FAILED  Resource CREATE failed:
> resources.Compute: Error: resources[0].resources.NetworkDeployment:
> Deployment to server failed: deploy_status_code: Deployment exited with
> non-zero status code: 1
> 2019-10-17 12:25:22Z [overcloud.Controller.0]: CREATE_FAILED  CREATE
> aborted
> 2019-10-17 12:25:22Z [overcloud.Controller]: UPDATE_FAILED  Operation
> cancelled
>
>  Stack overcloud CREATE_FAILED
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#23666):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/23666
> Mute This Topic: https://lists.opnfv.org/mt/34701811/1217375
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> pberber...@iol.unh.edu]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23675): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23675
Mute This Topic: https://lists.opnfv.org/mt/34701811/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #laas Downtime 8/22

[Parker Berberian]

Hi all,

LaaS at the UNH-IOL will be going down for maintenance on Thursday, August
22 at around 10 am Eastern time. You may lose VPN connection during this
time. I will be reaching out to active users individually as well to
confirm they are aware.

Thank you,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23466): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23466
Mute This Topic: https://lists.opnfv.org/mt/32967743/21656
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] LaaS Downtime July 24th (Tomorrow)

[Parker Berberian]

Hi all,

We will be doing some maintenance on our lab at UNH tomorrow. If you create
a new booking tomorrow, it may not be fulfilled until 5pm Eastern time. VPN
connection to existing hosts should not be affected.

BR,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23384): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23384
Mute This Topic: https://lists.opnfv.org/mt/32574359/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [XCI] Failed to deploy XCI

[Parker Berberian]

Hi Dan Xu,

This seems like a bug if XCI is not using `sudo` to change group settings.
However, you should be able to work around this by adding the groups to
your user manually.

In my XCI deploy, the deployment user has these groups: "root, wheel, kvm,
qemu, docker, libvirt". I'm not sure which are required by xci, but there
is no harm to adding them all to your user.

If you manually add these groups to your xd user with `sudo usermod -aG
 xd` then XCI should skip the step that is giving you trouble.

Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu


On Fri, Jul 12, 2019 at 3:42 AM xudan  wrote:

> Hi all,
>
>
>
> I tried to deploy with XCI master but failed with error “usermod:
> Permission denied.\nusermod: cannot lock /etc/passwd;”. The detailed error
> message and required ENV can be found in the attachment.
>
> I used user ‘xd’ and have added ‘xd ALL=(ALL) NOPASSWD:ALL’ to sudoers.
>
> Also SSH key are generated before the deploy.
>
> xd@ubuntu:~$ ll ~/.ssh/
>
> total 20
>
> drwxrwxr-x 2 xd xd 4096 Jul 11 15:17 ./
>
> drwxr-xr-x 7 xd xd 4096 Jul 11 15:05 ../
>
> -rw--- 1 xd xd 1675 Jul 11 14:59 id_rsa
>
> -rw-r--r-- 1 xd xd  391 Jul 11 14:59 id_rsa.pub
>
> -rw-r--r-- 1 xd xd  222 Jul 11 15:17 known_hosts
>
>
>
> Also I can successfully use command “sudo usermod –d /home/abc abc” to
> change user ‘abc’’s home with user ‘xd’.
>
>
>
> Did anyone meet the same problem before? Or do anyone know how to solve
> this?
>
>
>
> BR,
>
> Dan Xu
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#23360):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/23360
> Mute This Topic: https://lists.opnfv.org/mt/32439749/1217375
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> pberber...@iol.unh.edu]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23362): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23362
Mute This Topic: https://lists.opnfv.org/mt/32439749/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [opnfv-tsc] Opening nominations for the OPNFV Technical Steering Committee #election

[Parker Berberian]

Hi David,

I believe that there have been a handful of nominations that went to the
opnfv-tech-discuss and not the opnfv-tsc list. These nominations do not
seem to be included in your list. Perhaps they should be included?

Thank you,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu


On Sun, Jul 7, 2019 at 4:43 PM David McBride 
wrote:

> Team,
>
> Nominations close in two days (Tues, July 9).  We still do not have
> sufficient nominees to fill all of the TSC seats.  If you have at least a
> score of 20 on this list
> <https://wiki.opnfv.org/display/DEV/2019+Consolidated+Contributions>,
> please submit a nomination for someone who has not yet been nominated
> <https://wiki.opnfv.org/display/DEV/2019+Election+Nominees>.
>
> David
>
> On Fri, Jun 28, 2019 at 9:49 AM David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Team,
>>
>> We're nearly a week into the nomination period and I've only received two
>> nominations.  Remember that you may nominate yourself, or you may nominate
>> someone else. Nominations close July 9.  Thanks.
>>
>> David
>>
>> On Mon, Jun 24, 2019 at 5:19 PM David McBride <
>> dmcbr...@linuxfoundation.org> wrote:
>>
>>> Please send those nominations.
>>>
>>> Reminder that next week is the Independence Day holiday for the U.S., so
>>> for people in the U.S., please try to get those nominations in this week
>>> before you leave on holiday.  Thanks.
>>>
>>> David
>>>
>>> On Fri, Jun 21, 2019 at 2:50 PM David McBride <
>>> dmcbr...@linuxfoundation.org> wrote:
>>>
>>>> Today,
>>>>
>>>> In accordance with the schedule
>>>> <https://wiki.opnfv.org/display/DEV/2019+TSC+and+TSC+Chair+Election+Schedule+of+Activities>
>>>> approved by TSC, we begin nominations for a new TSC, consisting of 15
>>>> members, per the Community Election Procedure
>>>> <https://wiki.opnfv.org/display/DEV/Community+Election+Procedure>.  
>>>> Nominations
>>>> will close on July 9 at 5 p.m. (Pacific).
>>>>
>>>> Both the nominator and the nominee must be an active contributor,
>>>> defined as having a score of at least 20 on this list
>>>> <https://wiki.opnfv.org/display/DEV/2019+Consolidated+Contributions>.
>>>> Alternatively, per the election procedure, a person may be an active
>>>> contributor if an exception was requested for them by a PTL during the
>>>> active contributor data review period that concludes today.  This is
>>>> indicated by a comment in the notes column of the list
>>>> <https://wiki.opnfv.org/display/DEV/2019+Consolidated+Contributions>.
>>>>
>>>> You may nominate yourself, or another individual, as long as that
>>>> individual agrees to the nomination.  To submit a nomination, please reply
>>>> to this email and include the nominees name, organization, and a brief
>>>> statement about the nominees qualifications and contributions.
>>>>
>>>> As I received nominations, I will post the information to this wiki
>>>> page <https://wiki.opnfv.org/display/DEV/2019+Election+Nominees>.
>>>>
>>>> Thank you for your participation in this important activity for the
>>>> OPNFV community.  Please let me know if you have any questions.
>>>>
>>>> David
>>>>
>>>> --
>>>> *David McBride*
>>>> Release Manager, OPNFV
>>>> Mobile: +1.805.276.8018
>>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>>> Skype: davidjmcbride1
>>>> IRC: dmcbride
>>>>
>>>
>>>
>>> --
>>> *David McBride*
>>> Release Manager, OPNFV
>>> Mobile: +1.805.276.8018
>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>> Skype: davidjmcbride1
>>> IRC: dmcbride
>>>
>>
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#5379):
> https://lists.opnfv.org/g/opnfv-tsc/message/5379
> Mute This Topic: https://lists.opnfv.org/mt/32163207/1217375
> Mute #election: https://lists.opnfv.org/mk?hashtag=election=3499611
> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [
> pberber...@iol.unh.edu]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23339): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23339
Mute This Topic: https://lists.opnfv.org/mt/32391466/21656
Mute #election: https://lists.opnfv.org/mk?hashtag=election=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Lab as a Service Users Attending the ETSI Plugfest [ACTION NEEDED]

[Parker Berberian]

Hi all,

If you use  Lab as a Service and you will be attending the ETSI plugfest,
we need to set up Network Address Translation (NAT) so that you will be
able to use your machines through the HIVE VPN.

All you need to do is send me a private email confirming that you will
attend the plugfest and which hosts you will need access to. I will respond
with your NAT address.

This NAT address is the address you will use to reach your host on the ETSI
HIVE VPN. No configuration changes will be made to your machine.

Thank you,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23192): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23192
Mute This Topic: https://lists.opnfv.org/mt/31833289/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [opnfv-tsc] Project Proposal : Lab as a Service (LaaS)

[Parker Berberian]

Hi David,

Thank you for your input. We will not be attending this plugfest, but I
would be happy to run a remote session for those interested.

Thanks,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu


On Tue, May 21, 2019 at 4:42 PM David McBride 
wrote:

> Parker,
>
> That's great news.  I know we discussed something similar to this at the
> dev meeting prior to ONS.  I'd like to suggest that you or someone from the
> team schedule one or two sessions at Plugfest to discuss.  Thanks.
>
> David
>
> On Tue, May 21, 2019 at 12:09 PM Parker Berberian 
> wrote:
>
>> Hello OPNFV Community,
>>
>> As many of you may know, Lab as a Service has been serving the OPNFV
>> community by providing on demand access to a customizable hardware and
>> software stack. This allows developers a quick and easy way to run, test,
>> and proof of concept their projects.
>>
>> In order to improve this community resource and to contribute further to
>> the development, testing, and integration work of the OPNFV community, we
>> want to propose that Lab as a Service (LaaS) become an OPNFV Project.
>>
>> Our project proposal can be found on the OPNFV wiki:
>> https://wiki.opnfv.org/display/PROJ/Lab+as+a+Service
>>
>> We welcome the community's feedback. We would also like to discuss this
>> proposal on the OPNFV Technical Discussion call on June 3rd.
>>
>> Thank you,
>>
>> Parker Berberian
>>
>> Lead Developer
>>
>> UNH InterOperability Laboratory
>>
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>
>> pberber...@iol.unh.edu
>>
>> www.iol.unh.edu
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#5279):
>> https://lists.opnfv.org/g/opnfv-tsc/message/5279
>> Mute This Topic: https://lists.opnfv.org/mt/31700377/766177
>> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
>> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [
>> dmcbr...@linuxfoundation.org]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23164): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23164
Mute This Topic: https://lists.opnfv.org/mt/31712998/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Project Proposal : Lab as a Service (LaaS)

[Parker Berberian]

Hello OPNFV Community,

As many of you may know, Lab as a Service has been serving the OPNFV
community by providing on demand access to a customizable hardware and
software stack. This allows developers a quick and easy way to run, test,
and proof of concept their projects.

In order to improve this community resource and to contribute further to
the development, testing, and integration work of the OPNFV community, we
want to propose that Lab as a Service (LaaS) become an OPNFV Project.

Our project proposal can be found on the OPNFV wiki:
https://wiki.opnfv.org/display/PROJ/Lab+as+a+Service

We welcome the community's feedback. We would also like to discuss this
proposal on the OPNFV Technical Discussion call on June 3rd.

Thank you,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23162): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23162
Mute This Topic: https://lists.opnfv.org/mt/31700376/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #IOL #LaaS Power Outage

[Parker Berberian]

Hello All,

Over the weekend, the UNH-IOL who host LaaS lost power.
I just got everything back up, and you should all be able to reach your
machines as normal.

We apologize for any inconvenience.

Thank you,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23071): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23071
Mute This Topic: https://lists.opnfv.org/mt/31294598/21656
Mute #iol: https://lists.opnfv.org/mk?hashtag=iol=2783016
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [opnfv-tsc] [infra-wg][pharos] step down as Pharos PTL

[Parker Berberian]

Hi,

Thank you Julien for your kind words and your work as PTL.

I nominate Jack as new PTL.

-Parker

On Wed, Feb 27, 2019 at 9:35 AM Julien  wrote:

> Hi Pharos team,
>
> I'd like to step down Pharos PTL.
>
> I have worked for Pharos for several releases and served as the Pharos PTL
> in last year. My internal duty had some changes in the middle of last year,
> and I don't have enough time to still work as Pharos PTL. I don't have
> enough contributions recently either.
>
> Thanks to Parker, Trevor, Alex and Jack. LaaS can be released and served
> the community with your contribution. I'm regrated that I don't have any
> contributions to LaaS. Infra is very important in both community and my
> company. I would like to involve some activities in Pharos and give my
> contributions as possible.
>
> I hope the Pharos team will make more achievements in the future.
>
> With this email, I also call for nomination for the new PTL. If any
> committer would like to take the role, please announce your nomination by
> replying to this email.
>
> The new PTL nomination will be open for 2 weeks until 13 March. Then I
> will initiate a vote in the gerrit system.
>
> Best Regards,
> Julien
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#5063):
> https://lists.opnfv.org/g/opnfv-tsc/message/5063
> Mute This Topic: https://lists.opnfv.org/mt/30152547/1217375
> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub  [
> pberber...@iol.unh.edu]
> -=-=-=-=-=-=-=-=-=-=-=-
>


-- 

Parker Berberian

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22868): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22868
Mute This Topic: https://lists.opnfv.org/mt/30153051/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #laas #infra LaaS Upgrade - Deprecating labs.opnfv.org

[Parker Berberian]

Hello all,

As some of you may know, the Lab as a Service team has been working hard on
the second release of LaaS. LaaS 2.0 has many new features, such as
automated virtual deployments of OPNFV and allowing users to book multiple
servers as a "POD".

The newer version of the LaaS dashboard can be found at
https://labs.lfnetworking.org
The old dashboard, https://labs.opnfv.org, will soon be shut down. We will
honor all existing bookings, but we will not allow any new bookings through
that website. This will allow us to move the machines over to the newer
version of LaaS.

Thank you,
Parker Berberian

-- 

Parker Berberian

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22794): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22794
Mute This Topic: https://lists.opnfv.org/mt/29772137/21656
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Mute #infra: https://lists.opnfv.org/mk?hashtag=infra=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #infra #lass Late to meeting

[Parker Berberian]

Hi all,

I will be about 15 minutes late to the infra call today. With my new class
schedule, I would really appreciate moving the call an hour later (8 am PST
/ 11 am EST). This would match what is on the will too, I believe.

Thank you,
Parker
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22735): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22735
Mute This Topic: https://lists.opnfv.org/mt/29569572/21656
Mute #infra: https://lists.opnfv.org/mk?hashtag=infra=2783016
Mute #lass: https://lists.opnfv.org/mk?hashtag=lass=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] #compass Help installing Compass

[Parker Berberian]

Hi Harry,

Thank you for your feedback.

I appreciate that Fraser is no longer supported. I think it is important
for us as a community to come up with a better user experience in this
regard, however.

In my case, I am trying to use dovetail. But dovetail releases are delayed
because they can only compile their test cases after the reference OPNFV
platform for that version has been released.

So I am stuck in a position where dovetail only supports Fraser, but Fraser
is unsupported and (in my experience) broken by upstream changes almost
everywhere.

As both a "user" of OPNFV as someone trying to participate in the OVP, and
someone who will have to support OPNFV installations for Lab as a Service,
I think the release model of "you have to redeploy and rework your
infrastructure every few months" is not ideal.

I appreciate the work you and other installer teams put in, and this is
something that I think needs to be addressed by the community.

Thank you,
Parker

On Mon, Dec 17, 2018 at 10:23 PM harry huang 
wrote:

> Hi Parker
>
>
>
> We are not maintaining Fraser anymore, please use Gambia instead.
>
> LXC name and hostname are two different things. For example, in Gambia
> cinder LXC named hostx_cinder_api_container- but inside LXC the
> hostname is hostx-cinder-api-container-.
>
>
>
> Regards
>
> Harry
>
>
>
> *发件人**:* opnfv-tech-discuss@lists.opnfv.org [mailto:
> opnfv-tech-discuss@lists.opnfv.org] *代表 *Parker Berberian
> *发送时间:* 2018年12月15日 2:55
> *收件人:* opnfv-tech-dis. 
> *主题:* [opnfv-tech-discuss] #compass Help installing Compass
>
>
>
> Hello,
>
>
>
> I am trying to install Compass Fraser release. I am running into an issue
> late in the deployment process where the cinder api container on one of my
> controllers throws an exception. The problem seems to be that the LXC
> containers are given hostnames with underscores, which are rejected as
> invalid.
>
>
>
> According to the Openstack Oslo documentation (here
> <https://docs.openstack.org/oslo.config/pike/reference/types.html>),
> Parsing for HostAddress "Performs strict checks for both IP addresses and
> valid hostnames, matching the opt values to the respective types as per
> RFC1912"
>
>
>
> The mentioned RFC (here <https://tools.ietf.org/html/rfc1912>) states: "
> Allowable characters in a label for a host name are only ASCII letters,
> digits, and the `-' character."
>
>
>
>
>
>
>
> The exception I am getting is:  "oslo_config.cfg.DefaultValueError: Error
> processing default value host3_cinder_api_container-7534a57f for Opt type
> of HostAddress."
>
>
>
> The exception being raised on line 975 of oslo_config/cfg.py says
> "host3_cinder_api_container-7534a57f is not a valid hostname"
>
>
>
> Is there anything I can do here? Any help would be appreciated.
>
>
>
> Parker
>
>
>
>
>
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#22576):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/22576
> Mute This Topic: https://lists.opnfv.org/mt/28755686/1217375
> Mute #compass: https://lists.opnfv.org/mk?hashtag=compass=2783477
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> pberber...@iol.unh.edu]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22581): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22581
Mute This Topic: https://lists.opnfv.org/mt/28755686/21656
Mute #compass: https://lists.opnfv.org/mk?hashtag=compass=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #compass Help installing Compass

[Parker Berberian]

Hello,

I am trying to install Compass Fraser release. I am running into an issue
late in the deployment process where the cinder api container on one of my
controllers throws an exception. The problem seems to be that the LXC
containers are given hostnames with underscores, which are rejected as
invalid.

According to the Openstack Oslo documentation (here
),
Parsing for HostAddress "Performs strict checks for both IP addresses and
valid hostnames, matching the opt values to the respective types as per
RFC1912"

The mentioned RFC (here ) states: "
Allowable characters in a label for a host name are only ASCII letters,
digits, and the `-' character."



The exception I am getting is:  "oslo_config.cfg.DefaultValueError: Error
processing default value host3_cinder_api_container-7534a57f for Opt type
of HostAddress."

The exception being raised on line 975 of oslo_config/cfg.py says
"host3_cinder_api_container-7534a57f
is not a valid hostname"

Is there anything I can do here? Any help would be appreciated.

Parker
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22566): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22566
Mute This Topic: https://lists.opnfv.org/mt/28755686/21656
Mute #compass: https://lists.opnfv.org/mk?hashtag=compass=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] Infra Evolution: Labs

[Parker Berberian]

Hi Alec,

I believe your issue is that you are not selecting a lab. When you add a
host in the first step, you must also click "Select" on the lab at which
you want your booking to be (currently there is only one lab, but this is
expected to grow).

I have added a jira ticket to catch this error earlier.

And we have had discussions about implementing a rest api. You are right
that it would be easier to implement and use, but I think it will always be
for a niche userbase. As most people are going to be using the GUI, we want
to put most of our effort into making that better.

Let me ask you, what is the use case for a REST API? You mention CI/CD
jobs, and we have talked with Trevor Bramwell about the possibility of
integrating Jenkins into LaaS. This would involve basically implementing
some endpoint that jenkins can request resources from and we automatically
provision those machines as normal, but add them to the jenkins sandbox.
This would be very different from allowing the end user to end-to-end
automate booking, running code, and releasing the pod. Is this what you had
in mind? Because I think allowing for the later would require significant
development time, in not only the dashboard but in the labs themselves as
they would need to meet much stricter requirements about how they provide
access to your pods in a predictable and programmable way (currently we
just send out an email explaining the process).

Allowing a user to book a pod (and release it) through an api, in my
opinion, would give the users 80% of the benefit and only require 20% as
much time from us. The rest of the process (logging in and running
something) will most likely not be automatable in the near future.

Thank you very much for your feedback. We want very much to interact with
the community to create a product that is useful to us all.

-Parker

On Thu, Dec 13, 2018 at 6:39 PM Alec Hothan (ahothan) 
wrote:

> (Sorry for the SUSPICIOUS tagging and garbled links – these are inserted
> by annoying corp. email firewall and could not find a way to disable this)
>
>
>
> I hope there will be a plan to provide a REST API for LaaS, the GUI is
> pretty inconvenient, not easy to troubleshoot and impossible to automate. A
> REST API should be easier to do/test than implementing a GUI 
>
> Ideally, we should have CI/CD jobs that can bring up a test pod –
> configure it - run a  test – and release the pod, instead of requiring
> creation of long running pods that are not used often.
>
>
>
> Thanks
>
>
>
>Alec
>
>
>
>
>
> Hi Alec,
>
>
>
> I'm having trouble recreating the problem youre having.
>
> From the home page, try to first "Create a POD" and then create your
> booking using that pod.
>
> Your configuration works, and I just created a single pod machine to
> double check.
>
>
>
> We do not yet provide a rest interface to users.
>
>
>
> Thank you,
>
> Parker
>
>
>
> On Thu, Dec 13, 2018 at 12:26 PM Alec via Lists.Opnfv.Org
> 
>  wrote:
>
>
>
> Hi Lincoln,
>
>
>
> I am trying to book one pod with 1 host for now – just could not get
> passed the step of defining the network (see my other email).
>
> Once I’ll get it up and running I’ll be able to check the NIC.
>
> Would be great to have examples of pods/topologies, how they were
> configured (with UI snapshots or REST – whatever method was used).
>
>
>
> Thanks
>
>
>
> Alec
>
>
>
>
>
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22563): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22563
Mute This Topic: https://lists.opnfv.org/mt/28632364/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [SUSPICIOUS] Re: [SUSPICIOUS] Re: [opnfv-tech-discuss] Infra Evolution: Labs

[Parker Berberian]

Hi Alec,

I'm having trouble recreating the problem youre having.
>From the home page, try to first "Create a POD" and then create your
booking using that pod.
Your configuration works, and I just created a single pod machine to double
check.

We do not yet provide a rest interface to users.

Thank you,
Parker

On Thu, Dec 13, 2018 at 12:26 PM Alec via Lists.Opnfv.Org  wrote:

>
>
> Hi Lincoln,
>
>
>
> I am trying to book one pod with 1 host for now – just could not get
> passed the step of defining the network (see my other email).
>
> Once I’ll get it up and running I’ll be able to check the NIC.
>
> Would be great to have examples of pods/topologies, how they were
> configured (with UI snapshots or REST – whatever method was used).
>
>
>
> Thanks
>
>
>
> Alec
>
>
>
>
>
>
>
> *From: *Lincoln Lavoie 
> *Date: *Wednesday, December 12, 2018 at 12:44 PM
> *To: *"Alec Hothan (ahothan)" 
> *Cc: *Trevor Bramwell , "opnfv-tech-dis." <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject: *[SUSPICIOUS] Re: [SUSPICIOUS] Re: [opnfv-tech-discuss] Infra
> Evolution: Labs
>
>
>
> Hi Alec,
>
>
>
> I can answer some of the questions, Parker can confirm detailed specifics.
>
>
>
> There are two types of servers available in the UNH-IOL LaaS, Gigabyte and
> HPE.  The Gigabyte servers have 4x 10G interfaces, the HPE servers have 6x
> 10G interfaces.
>
>
>
> There are a couple of different linux distro images that can be selected /
> flashed onto each server.  Once flashed, you have root access and can make
> the changes you want to the servers kernel options, etc.
>
>
>
> One thing to note, right now, only PTL (project leaders) from an LFN
> project (with a proper info file) can book multiple servers (i.e. a pod
> with N >= 2).
>
>
>
> Cheers,
> Lincoln
>
>
>
>
>
>
>
> On Wed, Dec 12, 2018 at 8:21 PM Alec Hothan (ahothan) 
> wrote:
>
>
>
> Is there a pointer to the OPNFV LaaS beta? I’d like to check the L2
> configuration API along with bare metal inventory (more specifically what
> NIC cards and how many ports are available) + linux boot configurability (I
> need to check things like uio driver and huge pages can be configured). I
> will need all of these to be able to run nfvbench on LaaS.
>
> Thanks
>
>
>
>   Alec
>
>
>
>
>
> *From: *Lincoln Lavoie 
> *Date: *Friday, December 7, 2018 at 10:31 AM
> *To: *"Alec Hothan (ahothan)" 
> *Cc: *Trevor Bramwell , "opnfv-tech-dis." <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject: *[SUSPICIOUS] Re: [opnfv-tech-discuss] Infra Evolution: Labs
>
>
>
> Hi All,
>
>
> Responses in line below as well.
>
>
>
> Cheers,
> Lincoln
>
>
>
> On Fri, Dec 7, 2018 at 12:33 PM Alec via Lists.Opnfv.Org
> 
>  wrote:
>
> Hi Trevor,
>
>
>
> Inline…
>
>
>
>
>
>
>
>
>
>
>
> *From: * on behalf of Trevor Bramwell
> 
> *Date: *Thursday, December 6, 2018 at 4:47 PM
> *To: *"opnfv-tech-discuss@lists.opnfv.org" <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject: *[SUSPICIOUS] [opnfv-tech-discuss] Infra Evolution: Labs
>
>
>
> Hi all,
>
>
>
> The TSC tasked the Infra-WG to create a proposal for evolving the
>
> infrastructure of OPNFV, but given the low attendance to the Infra-WG
>
> calls I thought it best to bring this discussion to the mailing list so
>
> we can benefit from the wider community's experience and knowledge.
>
>
>
> To keep the discussion focused, I'd like to just look at Labs and how we
>
> can evolve the infrastructure there, and I'll follow up with thoughts on
>
> CI, code, and artifacts, after we've reached some consensus since there's a
>
> bit more interdependence with those components along with some
>
> complexity. I've collected some of the options here[1].
>
>
>
> What we need to find (and anyone feel free to jump in if I've
>
> misunderstood the ask) is a scalable solution for bringing up new PODs
>
> for CI that doesn't require us hosting or purchasing more dedicated
>
> hardware.
>
>
>
>
>
> Now of the top cloud providers: AWS, Google Compute, Azure, only AWS
>
> provides a hardware-as-a-service offering[2]. The others recently
>
> enabled nested virtualization on some instance types, which may work for
>
> us verifying virtual deployments (with performance trade-offs
>
> obviously), but don't help when we want to verify against networking
>
> hardware.
>
>
>
> That’s right.
>
>
>
> This is why I started the discussion with Packet.net. They appear to be
>
> the only provider that not only manages hardware for you, but provides
>
> an API for accessing and provisioning it.
>
>
>
> I agree with you regarding the convenience of a service like packet.net
> 

[opnfv-tech-discuss] Help Installing Apex

[Parker Berberian]

Hello all,

I am trying to install Apex Fraser on a Pharos POD. The deploy in failing
when trying to deploy the overcloud.
>From what I can tell, there is some sort of race condition in the init
scripts. The system tries to dhcp before the interface driver is loaded and
the link is up, putting the network unit in a failed state.

Relevant log output from one of the nodes:

Dec 10 17:39:09 localhost.localdomain network[1781]: Bringing up interface
eno4:
Dec 10 17:39:09 localhost.localdomain kernel: ixgbe :02:00.1:
registered PHC device on eno4
Dec 10 17:39:10 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
eno4: link is not ready
Dec 10 17:39:15 localhost.localdomain network[1781]: Determining IP
information for eno4... failed; no link present.  Check cable?
Dec 10 17:39:15 localhost.localdomain network[1781]: [FAILED]
Dec 10 17:39:16 localhost.localdomain kernel: ixgbe :02:00.1 eno4: NIC
Link is Up 10 Gbps, Flow Control: None
Dec 10 17:39:16 localhost.localdomain kernel: IPv6:
ADDRCONF(NETDEV_CHANGE): eno4: link becomes ready


As you can see, the interface eno4 only comes up one second after dhcp
fails.
DHCP does work, i.e. the machine can pxe boot using that interface just
fine. And I can manually log in and run `ifup eno4` and it gets an address
quickly - the problem is specific to the boot process.

Our jumphost was installed using the fraser 6.2 iso.

Any feedback welcome,

Parker
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22526): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22526
Mute This Topic: https://lists.opnfv.org/mt/28711622/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #laas #infra

[Parker Berberian]

Hello all,

I have been asked to give the community a short update on the status of Lab
as a Service.

A quick recap for those who have not been following LaaS - We are nearing
the release of a major upgrade that will allow users to design and book
whole "PODs" of machines together, instead of only using single servers.

As some of you may have noticed, hpe13 - hpe20 have been removed from the
current dashboard to allow for us to start testing LaaS 2.0. This testing
began today and we should be able to open up beta trials to users in the
next week or two. Sawyer and I will be working very hard over the next few
days to make sure the new dashboard and new backend are working properly.

The transition from the current system to the new system will happen
slowly. Once the new dashboard is publicly available, we will deprecate the
old dashboard. This will mean that no new bookings will be accepted through
the old dashboard. All machines will be added to the new system once the
existing bookings expire. We are going to try our best to make the
transition without shutting the whole lab down.

Thank you,

The UNH-IOL Lab as a Service Team
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22043): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22043
Mute This Topic: https://lists.opnfv.org/mt/25727424/21656
Mute #infra: https://lists.opnfv.org/mk?hashtag=infra=2783016
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

[Parker Berberian]

Hi Frank,

Depending on how much onus we want to put on the dashboard, we have three
different options as I see it:
1) user gives the URL to 'their' INFO file
2) user selected their project from a drop-down and the dashboard is able
to grab the INFO file from there
3) the dashboard maintains a list of users and projects internally and this
is all kept transparent to the user.

I think I prefer option 2, as that is a little more convenient to the user.
This will really only work, though, if they location of the INFO.yaml is
consistent for all projects.

Another question for us to consider is whether we want to restrict usage of
'top level' LFN projects. For example, would we allow e.g. ONAP users to
book all the machines, leaving none for onos, pnda, opnfv, etc.

Thanks,
Parker


On Tue, Aug 28, 2018, 2:58 AM Frank Brockners (fbrockne) 
wrote:

>
> IMHO it would be best to have the user provide the INFO.yaml link - and
> then just check that the repo belongs to an LFN project (just check the
> domain name).
> This mitigates the need to walk repo trees.
>
> We should also limit things to LFN projects, given that it is LFN that
> pays for the service. LFN projects (see https://www.lfnetworking.org/) are
>
> Opnfv.org
> Onap.org
> Opendaylight.org
> Fd.io
> Pnda.io
> Tungsten.io
> Snas.io
>
> Cheers, Frank
>
>
> -Original Message-
> From: Aric Gardner 
> Sent: Montag, 27. August 2018 21:06
> To: Parker Berberian 
> Cc: Frank Brockners (fbrockne) ; Lincoln Lavoie <
> lylav...@iol.unh.edu>; Trevor Bramwell ;
> opnfv-tech-dis. 
> Subject: Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage
> policy
>
> Hi Parker,
>
> Most LFN projects will have INFO files already, those that do not will
> have them added in the near future.
>
> The url to fetch the info files (or have the user provide them) is:
>
> https://raw.githubusercontent.com/$LFNproject/$repo/master/INFO.yaml
>
> LFNproject is one of
>
> onap
> opnfv
> acumos
> odl
> iotivity
> fdio
> hyperledger
>
> Regards,
> Aric
>
>
>
>
>
>
> On Mon, Aug 27, 2018 at 11:47 AM, Parker Berberian 
> wrote:
> > Hi all,
> >
> > This path makes sense to me.
> > Is there an official list of OPNFV / LFN projects for us to use?  I
> > can use all opnfv/* projects on github with INFO.yaml files. Will all
> > 7 LFN projects have a similar structure?
> >
> > Thanks,
> > Parker
> >
> > On Mon, Aug 27, 2018 at 11:20 AM, Frank Brockners (fbrockne)
> >  wrote:
> >>
> >> Hi Aric,
> >>
> >>
> >>
> >> I like that suggestion – and we might consider a tiered approach:
> >>
> >>
> >>
> >> ·   Single server booking: Open to all (like what we have right now)
> >>
> >> ·   Multi-server booking: Allow only PTLs to book resources. When
> >> booking, you need to supply a link to the INFO file on git to
> >> authorize yourself as PTL.
> >> With other projects also moving to INFO files, that would even work
> >> for other projects under the roof of the LFN. At the same time, there
> >> is only minimal burden on UNH – all they need to check is whether the
> >> UUID of the requesting user matches the PTL in the INFO file.
> >>
> >>
> >>
> >> Thoughts?
> >>
> >>
> >>
> >> Thanks, Frank
> >>
> >>
> >>
> >> From: opnfv-tech-discuss@lists.opnfv.org
> >>  On Behalf Of Aric Gardner
> >> Sent: Montag, 27. August 2018 17:11
> >> To: Parker Berberian 
> >> Cc: Lincoln Lavoie ; Trevor Bramwell
> >> ; opnfv-tech-dis.
> >> 
> >> Subject: Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage
> >> policy
> >>
> >>
> >>
> >> Hi Parker, Lincoln,
> >>
> >> Just a note, if we ask for a project name when booking we can turn
> >> that into a github url and grab that projects info file, which can
> >> inform us on things like project committers and project lead.
> >>
> >> example for project opnfv/releng:
> >> https://github.com/opnfv/releng/blob/master/INFO.yaml
> >>
> >> In this way we could limit bookings to committers, or if resources
> >> are indeed scarce, project leads.
> >>
> >> Regards,
> >>
> >> Aric
> >>
> >>
> >>
> >> On Mon, Aug 27, 2018 at 10:42 AM, Parker Berberian
> >>  wrote:
> >>
> >> Hi Trevor and Lincoln,
> >>
> >>
> >

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

[Parker Berberian]

Hi all,

This path makes sense to me.
Is there an official list of OPNFV / LFN projects for us to use?  I can use
all opnfv/* projects on github with INFO.yaml files. Will all 7 LFN
projects have a similar structure?

Thanks,
Parker

On Mon, Aug 27, 2018 at 11:20 AM, Frank Brockners (fbrockne) <
fbroc...@cisco.com> wrote:

> Hi Aric,
>
>
>
> I like that suggestion – and we might consider a tiered approach:
>
>
>
> ·   Single server booking: Open to all (like what we have right now)
>
> ·   Multi-server booking: Allow only PTLs to book resources. When
> booking, you need to supply a link to the INFO file on git to authorize
> yourself as PTL.
> With other projects also moving to INFO files, that would even work for
> other projects under the roof of the LFN. At the same time, there is only
> minimal burden on UNH – all they need to check is whether the UUID of the
> requesting user matches the PTL in the INFO file.
>
>
>
> Thoughts?
>
>
>
> Thanks, Frank
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org  opnfv.org> *On Behalf Of *Aric Gardner
> *Sent:* Montag, 27. August 2018 17:11
> *To:* Parker Berberian 
> *Cc:* Lincoln Lavoie ; Trevor Bramwell <
> tbramw...@linuxfoundation.org>; opnfv-tech-dis.  opnfv.org>
> *Subject:* Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage
> policy
>
>
>
> Hi Parker, Lincoln,
>
> Just a note, if we ask for a project name when booking we can turn that
> into a github url and grab that projects info file, which can inform us on
> things like project committers and project lead.
>
> example for project opnfv/releng: https://github.com/opnfv/
> releng/blob/master/INFO.yaml
>
> In this way we could limit bookings to committers, or if resources are
> indeed scarce, project leads.
>
> Regards,
>
> Aric
>
>
>
> On Mon, Aug 27, 2018 at 10:42 AM, Parker Berberian 
> wrote:
>
> Hi Trevor and Lincoln,
>
>
>
> I just want these points to be kept in mind:
>
> - Users can design and book 'PODs' of any size (up to a max that it TBD).
> Especially as LaaS expands beyond OPNFV, it may not be helpful to limit our
> thinking to just the Pharos spec.
>
> - a significant feature of this LaaS 2.0 release is the sharing of
> resources. We try to make it as easy as possible to have a POD owner share
> their resources with coworkers, team members, or other projects for
> integration, etc. For example, scenarios with ONAP development / testing
> happening on top of OPNFV as the VIM, it can be the case that multiple
> projects can share a POD and both get a lot of value from it. So if we want
> to limit booking on a per user / per project basis, we need to decide how
> shared resources count toward that cap.
>
>
>
> Thanks,
>
> Parker
>
>
>
> On Mon, Aug 27, 2018 at 9:21 AM, Lincoln Lavoie 
> wrote:
>
> Hi Trevor,
>
>
>
> Does the LFN accounting system (i.e. what the dashboard performs
> authentication against) have any info tied to a user for the LFN project
> they participate in? To limit to 4 bookings per project, we'd need a source
> of truth for that.  Another approach would be to present the user with a
> "drop down" list of which project the resource is for.  What I want to
> avoid is requiring UNH-IOL to make a decision point about what a booking is
> being used for, because we don't always have 100% visibility into what
> project states are, etc.
>
>
>
> Cheers,
> Lincoln
>
>
>
> On Fri, Aug 24, 2018 at 3:54 PM Trevor Bramwell <
> tbramw...@linuxfoundation.org> wrote:
>
> Hi Parker,
>
> From the minutes of this week's TSC call:
> http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/
> opnfv-meeting.2018-08-21-12.52.html
> they've deferred the agreement till next week.
>
> Assuming there is an agreement, and LaaS is open to all LFN members, I
> agree we will run into a scarcity of resources if we don't set some
> restrictions upon users/projects.
>
> So the question is, should this restriction be on a per-user, per-group,
> per-lfn-project basis, or some combination thereof?
>
> With 48 x86 and 14 aarch64 machines, we can have in total 8 Pharos
> compliant PODs (6 servers) booked at once (with 4 extra servers).
>
> Perhaps we restrict bookings to 1 per-user, 4 per-lfn-project, with a
> max of 2-weeks per-booking? You would have to do some calculations of
> which groups/projects a user belongs to in order to figure out when the
> quota is reached. This will also be somewhat hard as the limit might
> depend on either the number of servers in total, or the number of PODs
> and that would have to be a separate calculation
>
> I'm not 

Re: [opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

[Parker Berberian]

Hi Trevor and Lincoln,

I just want these points to be kept in mind:
- Users can design and book 'PODs' of any size (up to a max that it TBD).
Especially as LaaS expands beyond OPNFV, it may not be helpful to limit our
thinking to just the Pharos spec.
- a significant feature of this LaaS 2.0 release is the sharing of
resources. We try to make it as easy as possible to have a POD owner share
their resources with coworkers, team members, or other projects for
integration, etc. For example, scenarios with ONAP development / testing
happening on top of OPNFV as the VIM, it can be the case that multiple
projects can share a POD and both get a lot of value from it. So if we want
to limit booking on a per user / per project basis, we need to decide how
shared resources count toward that cap.

Thanks,
Parker

On Mon, Aug 27, 2018 at 9:21 AM, Lincoln Lavoie 
wrote:

> Hi Trevor,
>
> Does the LFN accounting system (i.e. what the dashboard performs
> authentication against) have any info tied to a user for the LFN project
> they participate in? To limit to 4 bookings per project, we'd need a source
> of truth for that.  Another approach would be to present the user with a
> "drop down" list of which project the resource is for.  What I want to
> avoid is requiring UNH-IOL to make a decision point about what a booking is
> being used for, because we don't always have 100% visibility into what
> project states are, etc.
>
> Cheers,
> Lincoln
>
> On Fri, Aug 24, 2018 at 3:54 PM Trevor Bramwell <
> tbramw...@linuxfoundation.org> wrote:
>
>> Hi Parker,
>>
>> From the minutes of this week's TSC call:
>> http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/
>> opnfv-meeting.2018-08-21-12.52.html
>> they've deferred the agreement till next week.
>>
>> Assuming there is an agreement, and LaaS is open to all LFN members, I
>> agree we will run into a scarcity of resources if we don't set some
>> restrictions upon users/projects.
>>
>> So the question is, should this restriction be on a per-user, per-group,
>> per-lfn-project basis, or some combination thereof?
>>
>> With 48 x86 and 14 aarch64 machines, we can have in total 8 Pharos
>> compliant PODs (6 servers) booked at once (with 4 extra servers).
>>
>> Perhaps we restrict bookings to 1 per-user, 4 per-lfn-project, with a
>> max of 2-weeks per-booking? You would have to do some calculations of
>> which groups/projects a user belongs to in order to figure out when the
>> quota is reached. This will also be somewhat hard as the limit might
>> depend on either the number of servers in total, or the number of PODs
>> and that would have to be a separate calculation
>>
>> I'm not sure what the answer is here, but I wanted to respond to at
>> least keep the discussion rolling.
>>
>> Regards,
>> Trevor Bramwell
>>
>>
>> On Fri, Aug 24, 2018 at 10:58:28AM -0400, Parker Berberian wrote:
>> > Hi all,
>> >
>> > As the release of LaaS 2.0 (info here
>> > <https://wiki.opnfv.org/display/INF/LaaS+Timeline>) nears, we need to
>> come
>> > to a conclusion on how we are going to limit access to the Lab as a
>> Service.
>> >
>> > Background info:
>> >
>> > LaaS usage is currently around 50-80%. As we open LaaS to all of LFN
>> and as
>> > we allow users to book multiple servers together as one "POD", we
>> expect to
>> > have a resource scarcity.
>> >
>> > We need some way of policing who is allowed to book how many machines,
>> and
>> > for how long.
>> >
>> >
>> > The infra call this monday has been cancelled, and we need to try and
>> come
>> > to a conclusion on this soon.
>> >
>> > Thank you,
>> > Parker
>> >
>> >
>> >
>>
>> 
>>
>>
>
> --
> 
> ***
> *Lincoln Lavoie*
> Senior Engineer, Broadband Technologies
>
> <https://www.iol.unh.edu>
> www.iol.unh.edu
> 21 Madbury Rd., Ste. 100, Durham, NH 03824
> <https://maps.google.com/?q=21+Madbury+Rd.,+Ste.+100,+Durham,+NH+03824=gmail=g>
> Mobile: +1-603-674-2755
> lylav...@iol.unh.edu
> <http://www.facebook.com/UNHIOL#>   <https://twitter.com/#!/UNH_IOL>
> <http://www.linkedin.com/company/unh-interoperability-lab>
>
> Ars sine scientia nihil est! -- Art without science is nothing.
> Scientia sine ars est vacua! -- Science without art is empty.
>
> Broadband Forum Gfast Certified Product List
> <https://www.broadband-forum.org/implementation/interop-certification/gfast-certified-products>
> 
> ***
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21850): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21850
Mute This Topic: https://lists.opnfv.org/mt/24945176/21656
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Mute #infra: https://lists.opnfv.org/mk?hashtag=infra=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #infra #laas Deciding on LaaS usage policy

[Parker Berberian]

Hi all,

As the release of LaaS 2.0 (info here
) nears, we need to come
to a conclusion on how we are going to limit access to the Lab as a Service.

Background info:

LaaS usage is currently around 50-80%. As we open LaaS to all of LFN and as
we allow users to book multiple servers together as one "POD", we expect to
have a resource scarcity.

We need some way of policing who is allowed to book how many machines, and
for how long.


The infra call this monday has been cancelled, and we need to try and come
to a conclusion on this soon.

Thank you,
Parker

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21839): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21839
Mute This Topic: https://lists.opnfv.org/mt/24945176/21656
Mute #infra: https://lists.opnfv.org/mk?hashtag=infra=2783016
Mute #laas: https://lists.opnfv.org/mk?hashtag=laas=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [pharos] Accessing Laas

[Parker Berberian]

Hi Raghuram,

The LaaS dashboard is found here: https://labs.opnfv.org/

There, you can view available development machines and follow the prompts
to book them.

- Parker

On Sun, Aug 19, 2018 at 6:28 AM, Raghuram Vadapalli  wrote:

> Hi,
>
> I am an intern who recently started working with opnfv. In order to try
> and deploy tripleo, I need access to a 16GB (preferrably 32GB) machine. Can
> you tell me how to access Laas.
> --
> Regards,
> Raghuram
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21805): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21805
Mute This Topic: https://lists.opnfv.org/mt/24733789/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [apex][auto] Apex on LaaS x86 server

[Parker Berberian]

Hi,

I'm not sure if it matters when doing a virtual install, but it seems that
the script Gerard linked does not change interface names in the network
settings file, while Mark's guide does.
The HPE LaaS servers have uncommon NIC names, so you will probably have to
set them in the config file because the default em1/eth1 will not match any
interface on the host.

-Parker

On Fri, Jul 27, 2018 at 10:55 AM, Mark Beierl  wrote:

> I’m not sure if this will help, but here are my notes for installing Apex
> on LaaS:
>
>
>
> https://wiki.opnfv.org/display/storperf/LaaS+Setup+For+Development#
> LaaSSetupForDevelopment-InstallOPNFVApex
>
>
>
> Note – this was tested only with the Fraser release.
>
>
>
> Regards,
>
> Mark
>
>
>
> *Mark Beierl*
>
> SW System Sr Principal Developer
>
> *Dell **EMC* | Cloud & Communication Service Provider Solution
>
> mark.bei...@dell.com
>
>
>
> *From: * on behalf of Gerard Damm <
> gerard.d...@wipro.com>
> *Date: *Thursday, July 26, 2018 at 18:21
> *To: *"opnfv-tech-discuss@lists.opnfv.org"  opnfv.org>
> *Subject: *[opnfv-tech-discuss] [apex][auto] Apex on LaaS x86 server
>
>
>
> Hello,
>
>
>
> I'm trying to use the Apex installer (basic virtual deployment) on a x86
> UNH Pharos LaaS server (CentOS).
>
> This would be used later as one of the infrastructure options for the Auto
> project (e.g., to provide
>
> Openstack instances for VNFs and for ONAP).
>
>
>
> I've been using commands such as those listed in this simple test script
> to automate the Apex installation (for virtual deployment):
>
> https://wiki.opnfv.org/pages/viewpage.action?pageId=26837081
>
>
>
> (based on https://docs.opnfv.org/en/stable-fraser/submodules/apex/
> docs/release/installation/virtual.html )
>
>
>
> I'm getting an Ansible playbook error for the deploy command:
>
> sudo opnfv-deploy -v -n network_settings.yaml -d deploy_settings.yaml
>
>
>
> Details:
>
> 304 ERROR: Ansible playbook failed. See Ansible logs for details.
>
> Traceback (most recent call last):
>
>   File "/bin/opnfv-deploy", line 10, in 
>
> sys.exit(main())
>
>   File "/usr/lib/python3.4/site-packages/apex/deploy.py", line 312, in
> main
>
> 'deploy_dependencies.yml'))
>
>   File "/usr/lib/python3.4/site-packages/apex/common/utils.py", line 141,
> in run_ansible
>
> raise Exception(e)
>
> Exception: Ansible playbook failed. See Ansible logs for details.
>
>
>
> Was there anything missing or incorrect in the sequence of commands from
> the test script ?
>
>
>
> Also, would it be possible to make section 13.2 a bit more explicit (i.e.,
> exactly which parts of the "Install Bare Metal Jump Host section" should be
> done ? Is it only section 11.1 ?). Or provide a sample complete
> installation script ?
>
>
>
> Are there any specific changes to be made to network_settings.yaml and/or
> deploy_settings.yaml ?
>
> (in the example, in deploy_settings.yaml, I replaced ha_enabled from true
> to false, and commented out "vim: 'openstack'" which was causing an error,
> and defaults to OpenStack anyway)
>
>
>
> Error with vim: 'openstack' :
>
> Traceback (most recent call last):
>
>   File "/bin/opnfv-deploy", line 10, in 
>
> sys.exit(main())
>
>   File "/usr/lib/python3.4/site-packages/apex/deploy.py", line 243, in
> main
>
> deploy_settings = DeploySettings(args.deploy_settings_file)
>
>   File "/usr/lib/python3.4/site-packages/apex/settings/deploy_settings.py",
> line 62, in __init__
>
> self._validate_settings()
>
>   File "/usr/lib/python3.4/site-packages/apex/settings/deploy_settings.py",
> line 94, in _validate_settings
>
> "specified".format(setting))
>
> apex.settings.deploy_settings.DeploySettingsException: Invalid
> deploy_option vim specified
>
>
>
>
>
> Thanks in advance for your help,
>
> Gerard
>
>
>
> Auto home wiki page:
>
> https://wiki.opnfv.org/pages/viewpage.action?pageId=12389095
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21636): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21636
Mute This Topic: https://lists.opnfv.org/mt/23827274/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] LaaS OPNFV at UNH-IOL power outage

[Parker Berberian]

Hi all,

Last night New Hampshire was hit with a pretty big thunderstorm and the
UNH-IOL that hosts LaaS lost power.

Our infrastructure is back up, and we are in the process of turning back on
all the machines. You should all have access again in a few minutes.

We apologize for any inconvenience this has caused.

Thank you for your patience,
Parker Berberian
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Request for Network Administration tools

[Parker Berberian]

Hi Mark,
I have taken a look at this tool and it is not clear to me that I could use
this to configure the Cisco switches. It seems to have the ability to
collect configuration information and update firmware, but would I be able
to e.g. add a set of ports to a vlan through the REST API?

Thank you,
Parker

On Tue, May 22, 2018 at 10:19 PM, Beierl, Mark <mark.bei...@dell.com> wrote:

> Hello, Parker.
>
> There is another, non OpenStack project, RackHD, which claims to support
> provisioning for Cisco.
>
> Here’s a note from one of their devs:
>
> Our team worked on cisco support for discovery, FW update and
> configuration. Here is the microservice code : https://github.com/RackHD/
> on-network
>
> It also has all the workflows hooks in RackHD workflow engine.
>
>
> If you’re interested in exploring that, I can be a point of contact to see
> what automation can be done with RackHD.
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Engineer
> *Dell **EMC* | Cloud & Communication Service Provider Solution
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> On May 22, 2018, at 17:31, MORTON, ALFRED C (AL) <a...@research.att.com>
> wrote:
>
> Hi Parker,
>
>
>
> OPNFV has a controller performance project, CPERF,
>
> which doesn’t participate in releases but continues its work
>
> on controller testing. The project is also a resource for collaboration
>
> between ODL and OPNFV when issues come up.  This sounds like
>
> yet another opportunity for collaboration.
>
>
>
> I’ve CC’d our PTL, Sai, and Daniel, Luis, and Jamo who are
>
> other Cperf regulars. Both Jamo and I attended the LaaS
>
> presentation you did with Jack at ONS 2018 and asked several questions.
>
>
>
> I’m taking some time off this week, but I’m sure a
>
> Cperf’er can help. We also have a mini-meeting at
>
> 2:15pm ET Thursday for more interactive discussions.
>
>
>
> regards,
>
> Al
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> mailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> <opnfv-tech-discuss-boun...@lists.opnfv.org>] *On Behalf Of *Parker
> Berberian
> *Sent:* Friday, May 18, 2018 12:41 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] Request for Network Administration tools
>
>
>
> Hi All,
>
>
>
> If you don't know me, I am Parker Berberian. I am running the Lab as a
> Service at the UNH Interoperability Lab.
>
>
>
> We are beginning development on supporting dynamic pod allocation. To do
> this, we need to be able to manipulate our underlay network in an automated
> fashion in order to create opnfv "pods" from any arbitrary machines we host.
>
>
>
> Essentially, when a deployment happens, we need to be able to take any of
> our available machines and add them to the appropriate vlans and make sure
> they can all talk to each other. There may be as many as 4 switches between
> different machines, so all the necessary switches need to be configured to
> forward the given vlans.
>
>
>
> We use Cisco 9300 switches (here
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.cisco.com_c_en_us_support_switches_nexus-2D92160yc-2Dswitch_model.html=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OfsSu8kTIltVyD1oL72cBw=ik2jOw_DuSMOkO9Zrh9cdyeohFVCXMOeJRYZgC7Uq1s=VSROTQeUD-ozUCQE_KP0x1tkW8174mIuQNcSDX05nfA=>)
> which support OpenFlow. So we originally considered used an SDN controller
> such as OpenDaylight.
>
>
>
> Has anyone used a tool that might accomplish what we need? Any
> recommendations are welcome.
>
>
>
> Thank you,
>
> Parker Berberian.
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Request for Network Administration tools

[Parker Berberian]

Hi All,

If you don't know me, I am Parker Berberian. I am running the Lab as a
Service at the UNH Interoperability Lab.

We are beginning development on supporting dynamic pod allocation. To do
this, we need to be able to manipulate our underlay network in an automated
fashion in order to create opnfv "pods" from any arbitrary machines we host.

Essentially, when a deployment happens, we need to be able to take any of
our available machines and add them to the appropriate vlans and make sure
they can all talk to each other. There may be as many as 4 switches between
different machines, so all the necessary switches need to be configured to
forward the given vlans.

We use Cisco 9300 switches (here
<https://www.cisco.com/c/en/us/support/switches/nexus-92160yc-switch/model.html>)
which support OpenFlow. So we originally considered used an SDN controller
such as OpenDaylight.

Has anyone used a tool that might accomplish what we need? Any
recommendations are welcome.

Thank you,
Parker Berberian.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on LaaS ARM

[Parker Berberian]

Mark,

You have to be mindful that ARM does not support nested virtualization (and
therefore virtual deployments with openstack are impossible). If Fuel does
not support Kubernetes, then you may be out of luck until we can provide
pharos POD's through LaaS.

Thanks,
Parker

On Fri, Apr 6, 2018 at 9:39 AM, Beierl, Mark  wrote:

> Hello, folks!
>
> I have reserved an Arm server (arm41) in the LaaS and it's ready.  I am
> wondering if anyone has a configuration file for deploying Fuel on a single
> Arm server that I can borrow for this?
>
> Or is there a better way to deploy Fuel on Arm, like re-using an existing
> Jenkins job?
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Developer
> *Dell **EMC* | Cloud & Communication Service Provider Solution
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] LAAS Downtime March 12th

[Parker Berberian]

This email is to notify the OPNFV community that the Lab as a Service
hosted at the UNH-IOL will go down for maintenance on Monday, March 12th.
The downtime is expected to last for the majority of the business day,
assuming east coast time (UTC -500).
Once the servers come back up, there should be no impact to the users.

Thank you,
The LaaS Team
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Auto] Re: All pods are pending when setting up kubernetes

[Parker Berberian]

Hi Harry Huang,

I can help you with whatever you need us at UNH to do.

I just want to clarify: Is this a connection issue you are having with our
vpn and network? Or are you having trouble with pod1 itself?

I can install Ubuntu for you, or try to troubleshoot the freezing issue.
Let me know what you need.

Thank you,
Parker Berberian

On Tue, Oct 17, 2017 at 1:21 PM, Tina Tsou <tina.t...@arm.com> wrote:

> Include UNH Lab...
>
>
> Thank you,
> Tina
>
> On Oct 16, 2017, at 11:33 PM, huangxiangyu <huangxiang...@huawei.com>
> wrote:
>
> HI Michael
>
>
>
> Currently I manage to bring up onap pods in our local lab and most of them
> are in running state. But there seem to be a rancher bug that block me in
> UNH lab.  Everything seems fine and throws no error when I created
> rancher-agent. Somehow pods in kube-system just keep getting stuck in
> pending state. I check the docker images and even images for these pods are
> not pulled.
>
> [root@pod1 ~]# kubectl get pods --all-namespaces -a
>
> NAMESPACE NAME   READY STATUS
> RESTARTS   AGE
>
> kube-system   heapster-4285517626-8r16j  0/1   Pending
>  0  20h
>
> kube-system   kube-dns-638003847-hkn34   0/3   Pending
>  0  20h
>
> kube-system   kubernetes-dashboard-716739405-n7x9l   0/1   Pending
>  0  20h
>
> kube-system   monitoring-grafana-2360823841-bfd5b0/1   Pending
>  0  1d
>
> kube-system   monitoring-influxdb-2323019309-mgnb5   0/1   Pending
>  0  1d
>
> kube-system   tiller-deploy-737598192-dq0pm  0/1   Pending
>  0  1d
>
>
>
> This new pod should be powerful enough but still installed centos. I used
> to have no problem when setting up undercloud in previous pod which is also
> a centos pod. Have you ever met this problem ? or maybe we should ask UNH
> lab to reinstall a Ubuntu OS.
>
>
>
> Thanks
>
> Harry Huang
>
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Auto] More RAM for Auto

[Parker Berberian]

Hi Tina,

I'm sorry for the trouble. You said that you are using one of our x86
virtual pods? All of our pods have 64GB of RAM available.

Can you please remind me what pod you are using?

Thank you,
Parker Berberian

On Tue, Sep 26, 2017 at 11:48 AM, Lincoln Lavoie <lylav...@iol.unh.edu>
wrote:

> Hi Tina,
>
> I'll check with Parker what we can do. For the virtual pods, we're limited
> on the total RAM in the host system.  We might be able to allocate a
> complete HW blade to a pod for you, and increase the RAM, at the cost of
> one less pod available for anyone else to use.
>
> The servers for the ARM pod have arrived, but we will need to work with
> you to select the network topology and get the servers and network
> installed.
>
> Cheers,
> Lincoln
>
> On Mon, Sep 25, 2017 at 10:32 AM, Tina Tsou <tina.t...@arm.com> wrote:
>
>> Dear Lincoln,
>>
>> So far Auto got 16G RAM x86 based pod from LaaS at UNH LoL. Since it is
>> ONAP verifications onto OPNFV, it needs more memory. Would you add some
>> more memory to it?
>>
>> The Arm based pod needs a couple of weeks before final arrival, because
>> of the lead time.
>>
>>
>> Thank you,
>> Tina
>> IMPORTANT NOTICE: The contents of this email and any attachments are
>> confidential and may also be privileged. If you are not the intended
>> recipient, please notify the sender immediately and do not disclose the
>> contents to any other person, use it for any purpose, or store or copy the
>> information in any medium. Thank you.
>>
>
>
>
> --
> 
> ***
> *Lincoln Lavoie*
> Senior Engineer, Broadband Technologies
>
> <https://www.iol.unh.edu>
> www.iol.unh.edu
> 21 Madbury Rd., Ste. 100, Durham, NH 03824
> Mobile: +1-603-674-2755
> lylav...@iol.unh.edu
> <http://www.facebook.com/UNHIOL#>   <https://twitter.com/#!/UNH_IOL>
> <http://www.linkedin.com/company/unh-interoperability-lab>
>
> Ars sine scientia nihil est! -- Art without science is nothing.
> Scientia sine ars est vacua! -- Science without art is empty.
> 
> ***
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss