VVP intends to participate in the Casablanca release
best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
___
onap-discuss mailing list
onap-discuss@lists.onap.org
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
Hi PTLs,
Following today TSC's meeting and the Pas of Beijing Release, LF is going to
create Beijing Branch on all repos that have not currently been branched.
In case you have some repos dedicated for Casablanca development and do not
need Beijing Branch, please let me know asap.
@All
Hi Paul,
Looks like you are following old instructions.
You probably have one node and there is a limitation of 110 pods per node.
Please follow the instructions that Roger suggested in his email (attached)
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a
Hi Borislav,
Thanks for the suggestion. My helm repo got fixed and I was able to install
ONAP but 30 pods are not running. I am using the cd.sh script written by
Michael O’Brien and following the ONAP on Kubernetes installation flow. Can you
please suggest something for this?
PFA – List of
ONAP and Acumos team, for the last 30 min we can use my zoom account for
desktop sharing if required (After the TSC meet ends at 1130)
http://Zoom.us/j/7939937123
/michael
-Original Appointment-
From: Michael O'Brien On Behalf Of DEY, SPONDON
Sent: Wednesday, June 6, 2018 12:57 PM
To:
Hi Gildas,
FYI..regarding the Portal project, below are the branches created for Beijing
release. The team already started working on the ‘master’ branch for Casablanca.
Portal have two repos:
* repo: 'portal'; branch: 'release-2.2.0'
* repo: 'portal/sdk'; branch: 'release-2.2.0'
We are joining now
_
From: OBRIEN, FRANK MICHAEL
Sent: Thursday, June 07, 2018 11:07 AM
To: DEY, SPONDON ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] FW: ACUMOS ELK logging strategy
ONAP and Acumos team, for the last 30 min we can use my
Multicloud/k8s is for Casablanca, not for Beijing.
Thanks
Srini
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Thursday, June 7, 2018 8:14 AM
To: onap-rele...@lists.onap.org
Cc: onap-discuss@lists.onap.org
Subject:
Hi Helpdesk,
Following TSC discussion on June 7, find in attachment the status of all ONAP
repo and their need for a "beijing" branch.
You will see that a lot has already been done.
Thanks,
Gildas
[HuaweiLogowithName]
Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
I missed this call, sorry. Will there be meeting notes posted soon? Thx.
—Raghu
On Jun 6, 2018, at 8:04 AM, VAN BRAKLE, TRACY L
mailto:tv8...@att.com>> wrote:
AGENDA for weekly recurring ONAP SDN-R team meeting Wednesday, June 6, 2018,
9am to 10am PDT
(1) Proposed PoC – Configuration
Thanks so much for gathering this information Gildas!
This is a great list!
I have few questions:
- Are the teams ok branching from the latest tip of master? (This will make it
easier on my script)
- Do the teams want me to tag the tip of the beijing branch with "2.0.0-ONAP"
tag?
Thanks!
Jess
Hey Jessica,
We have a bit of a glitch in releasing and tagging all at once. There is patch
https://gerrit.onap.org/r/#/c/50937/ which needs to be on the OOM Beijing
branch, but can only be tested and merged once beijing branches are created for
the repos referenced within this patch.
Is it
Hey Jessica,
We have a bit of a glitch in releasing and tagging all at once. There is patch
https://gerrit.onap.org/r/#/c/50937/ which needs to be on the OOM Beijing
branch, but can only be tested and merged once beijing branches are created for
the repos referenced within this patch.
Is it
Hi Jess,
Here u go.
- Are the teams ok branching from the latest tip of master? (This will make it
easier on my script) [Gildas] For the repos on which there is either a Docker
Release or a Java Released artifact, we should branch from that latest point.
For other repos we should branch
Hi Jess,
Here u go.
- Are the teams ok branching from the latest tip of master? (This will make it
easier on my script) [Gildas] For the repos on which there is either a Docker
Release or a Java Released artifact, we should branch from that latest point.
For other repos we should branch
Dear Mike..
Sorry i noticed this message a little bit late. I had created the beijing
branch for oom from the latest
tag available. But I can always remove it and re-create it from whichever point
you need.
Just let me know if I should proceed removing it.
Thanks!
Jess
> On Thu Jun 07
Dear Mike..
Sorry i noticed this message a little bit late. I had created the beijing
branch for oom from the latest
tag available. But I can always remove it and re-create it from whichever point
you need.
Just let me know if I should proceed removing it.
Thanks!
Jess
> On Thu Jun 07
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
Hi Jessica,
For vnfsdk-pkgtools, I think the 'beijing' tag should be applied to the current
master tip version. The 'release/mercury' came from pre Amsterdam release, it
came from Open-O.
Best Regards,
-Lianhao
-Original Message-
From: onap-discuss-boun...@lists.onap.org
Dear Mike..
Sorry i noticed this message a little bit late. I had created the beijing
branch for oom from the latest
tag available. But I can always remove it and re-create it from whichever point
you need.
Just let me know if I should proceed removing it.
Thanks!
Jess
On Thu Jun 07
Dear Gildas
All branches needed to be renamed from "Beijing" to "beijing" are now renamed.
All "beijing" branches have been created and tagged for all repos which my
script detected no
tag at all. These have been branched of from the tip of master. (See attached
list "all-no-tags")
All
Dear Gildas
All branches needed to be renamed from "Beijing" to "beijing" are now renamed.
All "beijing" branches have been created and tagged for all repos which my
script detected no
tag at all. These have been branched of from the tip of master. (See attached
list "all-no-tags")
All
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
24 matches
Mail list logo
