All:
For committers that are eligible to vote (https://wiki.opnfv.org/displa
y/DEV/OPNFV+Committers+List) in the Committer-at-Large TSC election, you
will be receiving an email from "Ray Paik (CIVS poll supervisor)" to cast
your vote. Please note that the email will not be coming from my Linux
Fo
Team,
Gerald K raised a good point: what do you do in the event that you have an
issue that you want to document, but which won't be resolved until some
indefinite release in the future?
To deal with this case, I've added a version to all of the projects called
"Future Release". So, if you don'
Morgan,
This is very helpful.
It would be great to add links to the last run to these pages, e.g.
http://testresults.opnfv.org/reporting/functest/release/master/index-status-joid.html
Seeing a stormy/cloudy icon, I want to immediately click on it to see what's
up. Is that in the plan? Let me kn
We need to be able to differentiate between issues that are intended for
some indefinite future release and those where the reporter, or the triage
team, has simply forgotten to fill in the field. On other projects, I've
used a release version called "future release," or similar. I think that
we
Sofia,
The copper sections for the common docs are ready for integration (userguide,
configguide in https://git.opnfv.org/cgit/copper/tree/docs).
I didn't see that there was a test run of the common guide when I submitted the
patches for review, so I haven't verified the formatting etc of the s
Can we wait for the next run in the official CI? If we are lucky, we already
get the green light. Then, we could immediately merge the other patches.
If there is no green light in the next CI run and we don’t see any issue with
the current code, then let’s be confident to merge the open patches.
Hi Folks,
Minutes of the meeting can be found here:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-19-14.04.html
Action items
hongbo to create the use case wiki for next week
rprakash and the ipv6 team to work on the development of the template.
rp
BEGIN:VCALENDAR
METHOD:CANCEL
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
DTSTART:16010101T02
Hi, Victor,
This is a common script for Functest. If
it's the bug as you mentioned, then all
features functest will have same issue.
Is there other feature functest also failed due to this?
Best Regards
Chaoyi Huang(joehuang)
发件人：viktor.tikkanen
收件人：黄朝意,opnfv-tech-discuss,
时间：2016-08-19 19:13:3
I think we should be confident to merge the open patches since they are
tested locally and also passed Viktor's test.
Furthermore, the patches in queue are split properly, it would not be too
difficult to revert in case there is any problem.
--
Yujun
On Fri, Aug 19, 2016 at 7:28 PM Ryota Mibu wr
Hi,
I have good news for you, let's keep doing our best.
[Report]
- Wenjuan rebased open patches, so that we can merge them promptly once we got
a green light in our CI.
- Viktor tested the doctor scenario in a Nokia pod and helped us with
debugging. Now, we got 'OK' (success) in the pod.
Hi!
It seems that "openstack endpoint list" command doesn't exit with 0. You can
remove " >/dev/null" from the following part of
/home/opnfv/repos/functest/ci/check_os.sh script:
echo "Checking OpenStack basic services:"
commands=('openstack endpoint list' 'nova list' 'neutron net-list' \
Hi Gerald,
In my opinion at least if there is no target release for an activity don’t mark
it with one. (leave it empty)
This allows you to use tags for your own projects purposes and for the release
activity to use tags for release purposes. No need to govern things in the
release proces
Hi David,
What about tasks that a project is not planning to fix in Colorado, nor D
release, but wants to keep the task as a reminder for a future release, i.e.
the fix version is not clear yet? In Doctor and Promise we had left the
“fixVersion” field empty for such cases. Which would be the re
Meeting ended Fri Aug 19 09:06:16 2016 UTC. Information about MeetBot at
http://wiki.debian.org/MeetBot . (v 0.1.4)
Minutes:
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-08-19-08.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/daisycloud/201
Hello,
How long for the time-out for openstack client request? And how to adjust the
configuration? I am afraid that the time-out setting is too short. For the
OpenStack catalog command is called before OpenStack endpoint list and succeed
in check_os.sh
Best Regards
Chaoyi Huang ( joehuan
16 matches
Mail list logo
