Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: New Update Infrastructure

  1. New Update Infrastructure

    We are happy to announce that a new SUSE update infrastructure is in place in Microsoft Azure. The update infrastructure operated and maintained by SUSE provides updates to instances launched from SUSE released SUSE Linux Enterprise Server on demand images in Microsoft Azure.

    Those using the latest images, released on 2014-11-06 or thereafter, will automatically connect to the new infrastructure. Those that have running instances started from images released prior to this date need to switch the instances to the new infrastructure. To switch a running instance follow these simple steps:

    -> wget http://104.45.147.201/instanceInfraUpgrade.noarch.rpm

    Then as root

    # zypper --no-refresh --non-interactive in instanceInfraUpgrade.noarch.rpm
    # instanceInfraUpgrade
    # rm instanceInfraUpgrade.noarch.rpm

    After the update to the new infrastructure "zypper lr" will point to repositories starting with "SMT"

    The old infrastructure server will be disabled on June 30, 2015.

    -- July 29, 2015 --
    I added the '--no-refresh' option to the zypper command to prevent zypper from trying to refresh the repositories. The old update infrastructure was removed on June 30th, as announced. Anyone trying to follow the procedure that still has the old update infrastructure configured will run into issues if the '--no-refresh' option is not used.
    Last edited by rjschwei; 29-Jul-2015 at 17:15. Reason: Clarify "latest images"

  2. Re: New Update Infrastructure

    Quote Originally Posted by rjschwei View Post
    The old infrastructure server will be disabled on June 30, 2015.
    The legacy infrastructure server is now offline. *If* you are experiencing any issues receiving updates, please check the procedure outlined above, for migrating to the new infrastructure, or start a new instance.

  3. #3

    Re: New Update Infrastructure

    Quote Originally Posted by bear454 View Post
    The legacy infrastructure server is now offline. *If* you are experiencing any issues receiving updates, please check the procedure outlined above, for migrating to the new infrastructure, or start a new instance.
    Is there something i missed? I can't install the rpm with the following errors


    zypper --non-interactive in instanceInfraUpgrade.noarch.rpm

    Refreshing service 'susecloud'.
    Problem retrieving the repository index file for service 'susecloud':
    Download (curl) error for 'http://azure-update.susecloud.net/repo/repoindex.xml?cookies=0':
    Error code: Connection failed
    Error message: Couldn't resolve host 'azure-update.susecloud.net'

    Check if the URI is valid and accessible.
    Retrieving repository 'SLE11-Security-Module' metadata [\]
    Download (curl) error for 'http://azure-update.susecloud.net/repo/$RCE/SLE11-Security-Module/sle-11-x86_64/repodata/repomd.xml':
    Error code: Connection failed
    Error message: Couldn't resolve host 'azure-update.susecloud.net'

  4. Re: New Update Infrastructure

    Quote Originally Posted by ericcwk View Post
    Is there something i missed?
    Please paste back the output of the following two commands (as root):
    Code:
    # dd if=/dev/sda bs=1c count=16 skip=65536 | hexdump
    
    # dd if=/dev/sda bs=1c count=16 skip=16384 | hexdump

  5. Re: New Update Infrastructure

    zypper is trying to refresh the existing repo, which fails. thus the whole process falls over. Run

    rm -rf /etc/zypp/repos.d/*

    first, then run

    zypper --non-interactive in instanceInfraUpgrade.noarch.rpm

  6. #6

    Re: New Update Infrastructure

    Quote Originally Posted by rjschwei View Post
    zypper is trying to refresh the existing repo, which fails. thus the whole process falls over. Run

    rm -rf /etc/zypp/repos.d/*

    first, then run

    zypper --non-interactive in instanceInfraUpgrade.noarch.rpm

    hi rjschwei

    After removing the existing repos, the command return similar response

    # zypper --non-interactive in instanceInfraUpgrade.noarch.rpm
    Refreshing service 'susecloud'.
    Problem retrieving the repository index file for service 'susecloud':
    Download (curl) error for 'http://azure-update.susecloud.net/repo/repoindex.xml?cookies=0':
    Error code: Connection failed
    Error message: Couldn't resolve host 'azure-update.susecloud.net'

    Check if the URI is valid and accessible.


    And i try to nslookup azure-update.susecloud.net
    it return to Server: 168.63.129.16
    Is it normal one ?

  7. Re: New Update Infrastructure

    Sorry, the given command only removes the repo, but leaves the service, which also needs to be removed:

    zypper rs susecloud

    We forgot to remove the DNS entry, that has now been taken care of.

  8. #8

    Re: New Update Infrastructure

    Hello, a question about this new update infrastructure (OK not so new now).

    Is this service hosted in the Azure DC for each region? We are operating from the North Europe (Dublin) region, and deploying the new SLES 11 SP4 images. Are there now SLES update servers deployed into North Europe for this purpose?

    We found that the SLES image has the registercloudguest script which executes when a new VM is deploying. This script tries to connect to SMT servers from /etc/regionserverclnt.cfg file by https protocol:

    # cat /etc/regionserverclnt.cfg
    [server]
    api = regionInfo
    certLocation = /var/lib/regionService/certs
    regionsrv = 104.45.154.114,104.45.31.195,191.237.254.253,23.10 0.36.229,23.101.26.184

    We are wondering where these IP addresses are hosted? We can see they are registered to Microsoft (via whois) but they are not listed in the published Microsoft range for North Europe.

    We need to conform to company IT Security policies, and so we need to understand where these servers are hosted, who is managing them.

    Many thanks!

  9. Re: New Update Infrastructure

    Those IP addresses are our geodistributed region servers. regionsrvclnt will request from (at least) one of the region servers, and it will respond with information about your local SMT servers, which, yes, run in each region.

    The IP addresses of all our servers are available via the `pint` command line tool; e.g. :
    Code:
    $ pint microsoft servers
    will return a list of the IP addresses for both the region servers and all SMT servers; you probably want
    Code:
    $ pint microsoft servers --regionserver
    $ pint microsoft servers --smt --region 'North Europe'
    in order to give you the global region servers (same as the list in the config file) and your region-local SMT servers.

    Just for reference, here's the current output:

    Code:
    $ pint microsoft servers --regionserver
    <?xml version='1.0' encoding='UTF-8'?>
    <servers>
      <server ip="23.101.26.184" name="" region="Southeast Asia" type="regionserver"/>
      <server ip="191.237.254.253" name="" region="Brazil South" type="regionserver"/>
      <server ip="104.45.31.195" name="" region="West Europe" type="regionserver"/>
      <server ip="104.45.154.114" name="" region="East US" type="regionserver"/>
      <server ip="23.100.36.229" name="" region="West US" type="regionserver"/>
    </servers>
    
    
    $ pint microsoft servers --smt --region 'North Europe'
    <?xml version='1.0' encoding='UTF-8'?>
    <servers>
      <server ip="104.45.85.11" name="smt-azure.susecloud.net" region="North Europe" type="smt"/>
      <server ip="104.45.85.45" name="smt-azure.susecloud.net" region="North Europe" type="smt"/>
    </servers>
    Have a lot of fun!

  10. #10
    Join Date
    May 2017
    Location
    Maryland
    Posts
    4

    Re: New Update Infrastructure

    Hi,

    I realize this is from 3 years ago, but is this still the current update infrastructure?

    I have inherited a few servers that are SLES 11 SP2 and I am getting the following error for all repositories that use "default-ec2-update.susecloud.net". I think the update script has not been run on the affected servers, would it still work or have there been additional changes, etc?

    "
    Warning: Disabling repository '{insert repo name}' because of the above error.
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/{insert repo name}/sle-11-x86_64/repodata/repomd.xml':
    Error code: Connection failed
    Error message: Couldn't resolve host 'default-ec2-update.susecloud.net'
    "

    Third party repositories refresh ok -- Nvidia (http://download.nvidia.com/novell/sle11sp2) and the "server-monitoring" (http://download.opensuse.org/reposit...ng/SLE_11_SP3/)


    repos with error:
    SLE11-SDK-SP1
    SLE11-SDK-SP1-Pool
    SLE11-SDK-SP1-Updates
    SLE11-SDK-SP2-Core
    SLE11-SDK-SP2-Updates
    SLE11-SDK-SP3-Pool
    SLE11-SDK-SP3-Updates
    SLE11-SP1-Debuginfo-Pool
    SLE11-SP1-Debuginfo-Updates
    SLE11-SP2-Debuginfo-Core
    SLE11-SP2-Debuginfo-Updates
    SLE11-SP2-WebYaST-13-Pool
    SLE11-SP2-WebYaST-13-Updates
    SLE11-SP3-Debuginfo-Pool
    SLE11-SP3-Debuginfo-Updates
    SLE11-WebYaST-SP1
    SLE11-WebYaST-SP1-Updates
    SLE11-WebYaST-SP2-Pool
    SLE11-WebYaST-SP2-Updates
    SLES11-Extras
    SLES11-SP1
    SLES11-SP1-Pool
    SLES11-SP1-Updates
    SLES11-SP2-Core
    SLES11-SP2-Extension-Store
    SLES11-SP2-Updates
    SLES11-SP3-Extension-Store
    SLES11-SP3-Pool
    SLES11-SP3-Updates

    Repo location
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/install/SLE11-SDK-SP1/sle-11-x86_64/media.1/media':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP2-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Pool/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP1-Debuginfo-Pool/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP1-Debuginfo-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP2-Debuginfo-Core/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP2-Debuginfo-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP2-WebYaST-1.3-Pool/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP2-WebYaST-1.3-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP3-Debuginfo-Pool/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP3-Debuginfo-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/install/SLE11-WebYaST-SP1/sle-11-x86_64/media.1/media':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP1-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP2-Pool/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP2-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-Extras/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/install/SLES11-SP1/sle-11-x86_64/media.1/media':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP1-Pool/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP1-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP2-Extension-Store/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP2-Updates/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP3-Extension-Store/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP3-Pool/sle-11-x86_64/repodata/repomd.xml':
    Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP3-Updates/sle-11-x86_64/repodata/repomd.xml':



    Quote Originally Posted by rjschwei View Post
    We are happy to announce that a new SUSE update infrastructure is in place in Microsoft Azure. The update infrastructure operated and maintained by SUSE provides updates to instances launched from SUSE released SUSE Linux Enterprise Server on demand images in Microsoft Azure.

    Those using the latest images, released on 2014-11-06 or thereafter, will automatically connect to the new infrastructure. Those that have running instances started from images released prior to this date need to switch the instances to the new infrastructure. To switch a running instance follow these simple steps:

    -> wget http://104.45.147.201/instanceInfraUpgrade.noarch.rpm

    Then as root

    # zypper --no-refresh --non-interactive in instanceInfraUpgrade.noarch.rpm
    # instanceInfraUpgrade
    # rm instanceInfraUpgrade.noarch.rpm

    After the update to the new infrastructure "zypper lr" will point to repositories starting with "SMT"

    The old infrastructure server will be disabled on June 30, 2015.

    -- July 29, 2015 --
    I added the '--no-refresh' option to the zypper command to prevent zypper from trying to refresh the repositories. The old update infrastructure was removed on June 30th, as announced. Anyone trying to follow the procedure that still has the old update infrastructure configured will run into issues if the '--no-refresh' option is not used.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •