Re: [opencontrail-dev] wiki.opencontrail.org

[Rhonda Eldridge]

This is the one that we use.

https://github.com/Juniper/contrail-controller/wiki

but it isn't associated with wiki.opencontrail.org.

Rhonda Eldridge
Director of Engineering

[cid:image006.jpg@01D190D5.B6EF1290]
Technica Corporation
22970 Indian Creek Drive, Suite 500, Dulles, VA 20166
Direct: 703-662-2124
Cell: 202-486-8311

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of CARVER, PAUL
Sent: Monday, May 15, 2017 9:46 AM
To: dev@lists.opencontrail.org
Subject: [opencontrail-dev] wiki.opencontrail.org

Does wiki.opencontrail.org exist? I'm getting a DNS resolution failure.

This link https://wiki.opencontrail.org/wiki/GerritJenkinsGit#Test_Failures 
appears in the Zuul message on a build failure (e.g. 
https://review.opencontrail.org/#/c/30895/ ) but the link is no good because 
the entire domain fails both a DNS and whois lookup.


___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] wiki.opencontrail.org

[CARVER, PAUL]

Does wiki.opencontrail.org exist? I'm getting a DNS resolution failure.

This link https://wiki.opencontrail.org/wiki/GerritJenkinsGit#Test_Failures 
appears in the Zuul message on a build failure (e.g. 
https://review.opencontrail.org/#/c/30895/ ) but the link is no good because 
the entire domain fails both a DNS and whois lookup.


___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] Slide deck from the OCUG meeting

[CARVER, PAUL]

Randy,

Thanks for your presentation at the Open Contrail Users Group last week. Can 
you please post a public link to your slide deck for people who were unable to 
attend or who didn't take phone photos of every slide. Especially, the link to 
the Google Group needs to go out so that everyone on the Dev mailing list can 
sign up.

I have a list of potential topics for the first meeting of whatever forum you 
end up organizing.


  *   Compiling Contrail from source - There has been a fair amount of 
discussion of this on the mailing list recently
 *   Discussion of issues people are encountering
 *   Build scripts
 *   Prerequisites
 *   Documentation of the build process
  *   Due dates
 *   An overview of current key dates in the process (blueprint, code 
complete, testing, documentation, beta, GA)
 *   Discussion of any changes that might help contributors plan better
 *   Dates for dates - set expectations on how and when the key dates for 
future releases will be set
 *   Missed date management - discussion of how slipped dates for Juniper's 
GA release impact community development
  *   Testing procedures
 *   Discussion of how third party developers should expect to interact 
with Juniper during the time period between code freeze and beta and GA
 *   Discussion of beta vs release candidate and whether there are process 
improvements needed in order to ensure that third party developers are able to 
catch and fix bugs in the features they are developing
 *   Overview of test framework, not just unit tests but functional and 
full stack automated tests
  *   Documentation
 *   How are non-Juniper developers expected to deliver documentation for 
features that they develop?
 *   When is documentation due?
  *   Core reviewer / TSC / meetings
 *   What are the expectations for a non-Juniper developer to become a core 
reviewer?
 *   Does Contrail have anything equivalent to a Technical Steering 
Committee?
 *   Are there any regularly scheduled meetings (e.g. on Slack/IRC or 
teleconference) for developers to sync up on progress of their changes, discuss 
code reviews, discuss bugs, etc
 *   Build system problems - How can non-Juniper contributors effectively 
troubleshoot issues like this: 
https://jenkins.opencontrail.org/job/ci-contrail-vrouter-systest-ubuntu14-mitaka/480/console



___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org