This is not meant to be an exhaustive guide. It will attempt to cover the parts of on-boarding that are unique to the SDN team.
IRC is our primary method of synchronous communication.
My goal is to give camptocamp-archive
access to the --strip-components
flag in a backwards-compatible way.
The examples below demonstrate that gini-archive
implemented --strip-components
in a backwards-incompatible way, while the code proposed in my PR is API backwards compatible with the current camptocamp-archive
code and adds access to the --strip-components
flag.
I took some time and clearly documented the ODL+OpenStack CI proposal | |
that I've bounced off of many of you in various meetings and IRC chats | |
recently. | |
## Proposal | |
### Objective | |
Have unstable ODL + stable OpenStack testing as a part of ODL's CI process. |
[~/integration/test/tools/VM_Tool]$ vagrant up centos | |
Bringing machine 'centos' up with 'virtualbox' provider... | |
==> centos: Importing base box 'chef/centos-7.0'... | |
[KProgress: 20% | |
[KProgress: 50% | |
[KProgress: 70% | |
[KProgress: 90% | |
[K==> centos: Matching MAC address for NAT networking... | |
==> centos: Checking if box 'chef/centos-7.0' is up to date... |
Trying to start a server in test mode in the Vagrant environment using the latest code from the pilot_dev
branch fails with:
vagrant@packer-debian-7:~/bot/bot$ ./start.py -Tsc
Using simulated hardware
Starting server
ctrl_server.py | __init__ | 91 | INFO | CtrlServer running in test mode
ir_hub.py | __init__ | 64 | ERROR | Unable to create front IR array
ir_hub.py | __init__ | 64 | ERROR | Unable to create right IR array
ir_hub.py | __init__ | 64 | ERROR | Unable to create back IR array
-----BEGIN PGP SIGNED MESSAGE----- | |
Hash: SHA512 | |
Mon Oct 21 01:49:00 EDT 2013 | |
Hello all, | |
For a number of reasons, I've recently set up a new OpenPGP key, and | |
will be transitioning away from my old one. |
I think this shows the commits on master that don't have cherry-picks on stable/li
[~/integration]$ git cherry -v origin/stable/lithium origin/master |grep "^+" 14:53:44
+ 3617698be9b6a68ccec6ec476f83e8acf3f00171 Incrementing versions by 0.1.0 for post-lithium master branch
+ 3fbb50ad6f771d29dc1ad859955dfe79d6dab954 Add Reservation to Integration
+ 2038520177b9a28c72a60f868fa80538e01b11e1 replacing the usage of private RequestsiLibrary to system one
+ 9070f76aadadc6336d2be54b2134376c8ec2f427 Move odl-sfcofl2 from compatible-with-all.
Given that OpenDaylight is 2.5 years old, there was a common belief among Board members that there are capable, seasoned technical leaders within the OpenDaylight developer community from which a valid and robust TSC could be formed without the need for Platinum Member designates.
+1, I think we have a mature enough community now to build a TSC based on metrics more ideal than sponsorship, like popular votes (committer-at-large style), elected technical positions (like PTLs) and possibly specific key positions (like release manager or Int/Test PTL).
Daniel Farrell will give an OPNFV Summit talk at about the need to move towards Continuous Delivery (CD) in open source Software Defined Networking (SDN) and Network Function Virtulization (NFV) projects. In particular, projects that are integrated by the Open Platform for Network Function Virtulization (OPNFV) need to provide frequent, testable releases for OPNFV's Continuous Integration (CI) testing. OpenDaylight's delivery pipelines, built largely to meet this demand from OPNFV, will be used as examples.
With the continued development of SDN projects and the advent of integration-focused projects like OPNFV, new requirements have been imposed on upstreams. OPNFV can only test the upstream projects it integrates as frequently as they provide testable release artifacts. Infrequent releases will result in re-testing the same artifacts over-and-over again in CI, hiding breakages until a release and negating many of the benefits of CI. Developers making
I hereby claim:
To claim this, I am signing this object: