[opnfv-tech-discuss] Fwd: [Apex] Bare Metal Failure: pxelinux.cfg empty dir

Hi Tim - /tftpboot/pxelinux.cfg/ is empty The inventory mac_address matches the BMC MAC address.(see below) BUT I just noticed in the photos that Ironic is trying to boot via LAN 1, not the IPMI port, on both nodes. Node 1 photo: attempting to boot from MAC 0c:c4:7a:9d:7b:d0 Node 2 photo:

Re: [opnfv-tech-discuss] [Apex] Bare Metal Failure: pxelinux.cfg empty dir

Tim - I changed the inventory.yaml to use the mac_address of LAN port 1 (the port Ironic was using to try to boot the node). Still the same issue of /tftpboot/pxelinux.cfg/ being an empty directory - no directories nor files created for the nodes. At what point in the process is that directory

[opnfv-tech-discuss] Canceled: [barometer] Weekly Call

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:GMT Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:+0100 TZOFFSETTO:+ RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T01

[opnfv-tech-discuss] [Apex] Bare Metal Failure: pxelinux.cfg empty dir

Hi all - I'm trying to deploy Apex on a NUC (Jumphost) and 2 Super Micros (control, compute). Tim helped me through a networking issue last week, but now the process is running into a snag with Ironic. It looks like Ironic is trying to boot the nodes but is failing to find the relevant file in

[opnfv-tech-discuss] [dovetail] Dovetail documentation discussion scheduled on day 2 of PlugFest 9:00-10:00 AM

Just want to send a notice out as this is added at the end of day 1. We'll use this time to agree on how to structure various documents so that we can start to submit doc source to the repo. Please check out the plugfest schedule page. Thanks. Wenjing

Re: [opnfv-tech-discuss] [Apex] Bare Metal Failure: pxelinux.cfg empty dir

Hi Aimee, On your undercloud can you go to /tftpboot/pxelinux.cfg/ when you deploy? What folders/files are in there? Did you verify 0c-c4-7a-9d-7b-d0 matches the mac you entered in your inventory file? Thanks, Tim Rozet Red Hat SDN Team - Original Message - From: "Aimee Ukasick"

[opnfv-tech-discuss] [release][danube] Danube 2.0 release NEXT WEEK (May 4)

Team, The Danube 2.0 release is next week. Please make sure that the intent-to-release column for Danube 2.0 on the scenario status page is up to date. Also, please remember that ALL scenarios that were released in Danube 1.0 will

Re: [opnfv-tech-discuss] Canceled: [ovsnfv] Weekly Meeting

OK, see you in 2 weeks if there is no conflict with openstack schedule that day. On 04/24/2017 10:03 AM, O Mahony, Billy wrote: Hi All, Cancelling due to hackfest. If there are items you would like to see on the agenda, please jot them down here: _https://etherpad.opnfv.org/p/ovsnfv-meet_

[opnfv-tech-discuss] Canceled: Infra Working Group Meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT

[opnfv-tech-discuss] Canceled: [ovsnfv] Weekly Meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:UTC BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+ TZOFFSETTO:+ END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+ TZOFFSETTO:+ END:DAYLIGHT END:VTIMEZONE

[opnfv-tech-discuss] [ovsnfv] Weekly Meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:UTC BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+ TZOFFSETTO:+ END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+ TZOFFSETTO:+ END:DAYLIGHT END:VTIMEZONE

Re: [opnfv-tech-discuss] [release][euphrates] schedule change for MS1

Gentle reminder... Euphrates MS1 is just over one week away (May 2). David On Wed, Apr 12, 2017 at 2:22 AM, David McBride wrote: > Team, > > As you know, Milestone 1 is the deadline for intent-to-participate, and > for project release plans. On the TSC call