Send Starlingx-discuss mailing list submissions to
        starlingx-discuss@lists.starlingx.io

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
or, via email, send a message with subject or body 'help' to
        starlingx-discuss-request@lists.starlingx.io

You can reach the person managing the list at
        starlingx-discuss-owner@lists.starlingx.io

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Starlingx-discuss digest..."


Today's Topics:

   1. Re: Automated Notification for: [mirror-downloader][#119]
      Missing packages - Results report (Cordoba Malibran, Erich)
   2. Re: Automated Notification for: [mirror-downloader][#119]
      Missing packages - Results report (Xie, Cindy)
   3. Re: Automated Notification for: [mirror-downloader][#119]
      Missing packages - Results report (Rowsell, Brent)
   4. Re: Compute boot-loop (von Hoesslin, Volker)
   5. Re: Compute boot-loop (Michel Thebeau)
   6. Re: Propose OpenStack/Apmec to StarlingX like an upstream
      component (Dean Troyer)
   7. Re: Compute boot-loop (Alonso, Juan Carlos)


----------------------------------------------------------------------

Message: 1
Date: Thu, 1 Nov 2018 13:11:37 +0000
From: "Cordoba Malibran, Erich" <erich.cordoba.malibran@intel.com>
To: "starlingx-discuss@lists.starlingx.io"
        <starlingx-discuss@lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Automated Notification for:
        [mirror-downloader][#119] Missing packages - Results report
Message-ID: <4EA80D98-75AF-4DB1-A6B4-9ED5FAC99FC6@intel.com>
Content-Type: text/plain; charset="utf-8"

Lighttpd was upgraded in upstream:

Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src

We'll send a patch for master today. Should we backport this to r/2018.10 branch?

-Erich

On 11/1/18, 3:37 AM, "aragorn@intel.com" <aragorn@intel.com> wrote:

    [mirror-downloader][#119] Missing packages. Results report:
     - Missing: logs/L1_srpms_missing_centos.log
    lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key:
    ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d)


------------------------------

Message: 2
Date: Thu, 1 Nov 2018 13:53:00 +0000
From: "Xie, Cindy" <cindy.xie@intel.com>
To: "Cordoba Malibran, Erich" <erich.cordoba.malibran@intel.com>,
        "starlingx-discuss@lists.starlingx.io"
        <starlingx-discuss@lists.starlingx.io>, "Liu, ZhipengS"
        <zhipengs.liu@intel.com>
Subject: Re: [Starlingx-discuss] Automated Notification for:
        [mirror-downloader][#119] Missing packages - Results report
Message-ID:
        <2FD5DDB5A04D264C80D42CA35194914F35DB1360@SHSMSX104.ccr.corp.intel.com>

Content-Type: text/plain; charset="utf-8"

+ Zhipeng
We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework?

Thx. - cindy

-----Original Message-----
From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com]
Sent: Thursday, November 1, 2018 6:12 AM
To: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report

Lighttpd was upgraded in upstream:

Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src

We'll send a patch for master today. Should we backport this to r/2018.10 branch?

-Erich

On 11/1/18, 3:37 AM, "aragorn@intel.com" <aragorn@intel.com> wrote:

    [mirror-downloader][#119] Missing packages. Results report:
     - Missing: logs/L1_srpms_missing_centos.log
    lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key:
    ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d)

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

------------------------------

Message: 3
Date: Thu, 1 Nov 2018 13:55:36 +0000
From: "Rowsell, Brent" <Brent.Rowsell@windriver.com>
To: "Xie, Cindy" <cindy.xie@intel.com>, "Cordoba Malibran, Erich"
        <erich.cordoba.malibran@intel.com>,
        "starlingx-discuss@lists.starlingx.io"
        <starlingx-discuss@lists.starlingx.io>, "Liu, ZhipengS"
        <zhipengs.liu@intel.com>
Subject: Re: [Starlingx-discuss] Automated Notification for:
        [mirror-downloader][#119] Missing packages - Results report
Message-ID:
        <2588653EBDFFA34B982FAF00F1B4844EBB2F0821@ALA-MBD.corp.ad.wrs.com>
Content-Type: text/plain; charset="utf-8"

This needs to be functionally tested before it is pushed.

Brent

-----Original Message-----
From: Xie, Cindy [mailto:cindy.xie@intel.com]
Sent: Thursday, November 1, 2018 9:53 AM
To: Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>; starlingx-discuss@lists.starlingx.io; Liu, ZhipengS <zhipengs.liu@intel.com>
Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report

+ Zhipeng
We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework?

Thx. - cindy

-----Original Message-----
From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com]
Sent: Thursday, November 1, 2018 6:12 AM
To: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report

Lighttpd was upgraded in upstream:

Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src

We'll send a patch for master today. Should we backport this to r/2018.10 branch?

-Erich

On 11/1/18, 3:37 AM, "aragorn@intel.com" <aragorn@intel.com> wrote:

    [mirror-downloader][#119] Missing packages. Results report:
     - Missing: logs/L1_srpms_missing_centos.log
    lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key:
    ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d)

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

------------------------------

Message: 4
Date: Thu, 1 Nov 2018 16:12:26 +0000
From: "von Hoesslin, Volker" <Volker.Hoesslin@swsn.de>
To: "'starlingx-discuss@lists.starlingx.io'"
        <starlingx-discuss@lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Compute boot-loop
Message-ID: <DB39DAB5F762704A93D316F9CE7D021E4280986F@emilio.sis.net>
Content-Type: text/plain; charset="utf-8"

Maybe it helps: https://ibb.co/n2OgoL

----------------------------------------------------------------
Hello, there,
i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop.
Error messages are not really noticeable, except:
compute-X 'ceilometer-polling' process has failed. Auto recovery in progress

any suggestions? Greez & thx, volker...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181101/23258d92/attachment-0001.html>

------------------------------

Message: 5
Date: Thu, 1 Nov 2018 12:28:53 -0400
From: Michel Thebeau <michel.thebeau@windriver.com>
To: "von Hoesslin, Volker" <Volker.Hoesslin@swsn.de>,
        "'starlingx-discuss@lists.starlingx.io'"
        <starlingx-discuss@lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Compute boot-loop
Message-ID: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed

Hi Volker,

Could you describe the instructions you were using to setup startlingx
(were you following a wiki online)?  Did you recheck the instructions
versus what is actually configured on the computes?

How many cpus do your computes have?

Which build are you using?  Did you build your own?

When reboot-loop happens on a node often the error will be presented on
the console during boot or could be inferred from console, sometimes
referring to puppet logs of the node /var/log/puppet/

M


On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote:
> Hello, there,
> i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop.
> Error messages are not really noticeable, except:
> compute-X 'ceilometer-polling' process has failed. Auto recovery in progress
>
> any suggestions? Greez & thx, volker...
>
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss@lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss




------------------------------

Message: 6
Date: Thu, 1 Nov 2018 12:16:18 -0500
From: Dean Troyer <dtroyer@gmail.com>
To: doantungbk.203@gmail.com
Cc: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX
        like an upstream component
Message-ID:
        <CAOJFoEuSxPNOQto5oVmmFVP+zDtcKq0+oUXDP36W+hG6A1RjNA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

On Thu, Nov 1, 2018 at 7:44 AM Tung Doan <doantungbk.203@gmail.com> wrote:
> I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec project. Since we acknowledged the potential integration between Apmec and StarlingX, I am writing this email to propose adding OpenStack/Apmec to StarlingX like an upstream project.
>
> Project description: OpenStack Apmec [1] stands for the Automated Provisioning Framework for Multi-access Edge Computing which is the first orchestration and management framework dedicated to the MEC services in OpenStack. Below are some of the outstanding features of Apmec project:

I believe Apmec is not an official OpenStack project (as listed in
[0]), do you have plans to apply to become an official OpenStack
project under TC governance?  (Until then you do need to be careful
about referring to Apmec as 'an OpenStack project', it is hosted by
OpenStack, but is not (yet?) an OpenStack project.)

> - no need to take care of the NFV functionalities. Since existing NFV MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating them can make StarlingX complicated. Apmec was designed to take over responsibility for integrating them since the delivery of MEC services is our critical mission.

Is this replacing existing StarlingX functionality?

>  - no need to take care of the life-cycle management of the MEC applications. Apmec offers API to help StarlingX perform this function.  As mentioned earlier, Apmec is OpenStack project, therefore, to provide low-latency for MEC applications,  Apmec is also planned to support acceleration technologies (e.g, integrated with OpenStack Cyborg) such as DPDK and FPGA.

Can you get more specific about what the integration with StarlingX looks like?

dt

[0] https://governance.openstack.org/tc/reference/projects/index.html

--

Dean Troyer
dtroyer@gmail.com



------------------------------

Message: 7
Date: Thu, 1 Nov 2018 22:38:40 +0000
From: "Alonso, Juan Carlos" <juan.carlos.alonso@intel.com>
To: Michel Thebeau <michel.thebeau@windriver.com>, "von Hoesslin,
        Volker" <Volker.Hoesslin@swsn.de>,
        "'starlingx-discuss@lists.starlingx.io'"
        <starlingx-discuss@lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Compute boot-loop
Message-ID:
        <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com>

Content-Type: text/plain; charset="utf-8"

Hi,

I think you set up a Duplex system (two controllers), right?

I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso
I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso.

Please set up again a Duplex system with today's ISO to see if issue is still presented.

Regards.
Juan Carlos Alonso

-----Original Message-----
From: Michel Thebeau [mailto:michel.thebeau@windriver.com]
Sent: Thursday, November 1, 2018 10:29 AM
To: von Hoesslin, Volker <Volker.Hoesslin@swsn.de>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Compute boot-loop

Hi Volker,

Could you describe the instructions you were using to setup startlingx (were you following a wiki online)?  Did you recheck the instructions versus what is actually configured on the computes?

How many cpus do your computes have?

Which build are you using?  Did you build your own?

When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/

M


On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote:
> Hello, there,
> i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop.
> Error messages are not really noticeable, except:
> compute-X 'ceilometer-polling' process has failed. Auto recovery in progress
>
> any suggestions? Greez & thx, volker...
>
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss@lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

------------------------------

Subject: Digest Footer

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


------------------------------

End of Starlingx-discuss Digest, Vol 6, Issue 3
***********************************************