From Michael.Brookhuis at suse.com Mon Apr 6 07:51:07 2020 From: Michael.Brookhuis at suse.com (Michael Brookhuis) Date: Mon, 6 Apr 2020 13:51:07 +0000 Subject: [manager-beta] Unable to install system with yomi Message-ID: Hi, When trying to install a system with yomi I end up with an error. During the first installation I received the following error: Failed to fetch tftp://server-address/pxe-yomi-image/image.md5 This aborts the installation. Known issue, am I doing something wrong or should I open a bug? From Michael.Brookhuis at suse.com Mon Apr 6 07:55:39 2020 From: Michael.Brookhuis at suse.com (Michael Brookhuis) Date: Mon, 6 Apr 2020 13:55:39 +0000 Subject: [manager-beta] Unable to install system with yomi --solved In-Reply-To: References: Message-ID: <9098c903-ea65-f7dd-a4a3-c9a0fcba280e@suse.com> Found my mistake. Forgot to enter my IP address in the distro. On 4/6/20 3:51 PM, Michael Brookhuis wrote: > Hi, > > When trying to install a system with yomi I end up with an error. During > the first installation I received the following error: > Failed to fetch tftp://server-address/pxe-yomi-image/image.md5 > > This aborts the installation. > > Known issue, am I doing something wrong or should I open a bug? > _______________________________________________ > manager-beta mailing list > manager-beta at lists.suse.com > Check the mailing list archive or Unsubscribe at http://lists.suse.com/mailman/listinfo/manager-beta > From aplanas at suse.com Tue Apr 7 02:34:23 2020 From: aplanas at suse.com (Alberto Planas Dominguez) Date: Tue, 7 Apr 2020 08:34:23 +0000 Subject: [manager-beta] Unable to install system with yomi In-Reply-To: References: Message-ID: > Found my mistake. Forgot to enter my IP address in the distro. Right, this part is commented in the doc. Note that once the node gets provisioned and reboot, you will not have a susemanager.conf that contains the SUMA key as a grain. For me is not very clear how to bootstrap a node in SUMA provisioned with Yomi in a clear an easy way, this part is still WIP. If you have feedback, please share! From Michael.Brookhuis at suse.com Wed Apr 8 00:59:29 2020 From: Michael.Brookhuis at suse.com (Michael Brookhuis) Date: Wed, 8 Apr 2020 06:59:29 +0000 Subject: [manager-beta] Unable to install system with yomi In-Reply-To: References: Message-ID: <60e04ff4-6383-cb64-203d-66701b072628@suse.com> Hi, I am using the sles15 version. I will receive a pop-up how to register against SCC but no system will be registered with SALT. Then logging into that server I see that the master has been set to salt. This means that you have to have a DNS entry for salt. This is in my opinion a very bad idea. The master should be given with a parameter during boot. After changing the master in master.conf to my SUSE Manager Server and restarting the salt-minion, the system appears. Configuring the formulas show that there is still a lot to be done. Some examples: Yomi Storage: - when selecting btrfs for /, I would expect that the default sub-volumes are set automatically. This is not the case. - filesystem xfs is not present. And this is mostly used especially for data volumes. Yomi Software: - I would expect that I can select software channels that are present in SUSE Manager. I think we should use what is available as distribution repositories. They can then be used during installation. - If then the channels are selected from within SUSE Manager, it should be easy to display the available patterns to be installed. This should be done via checkboxes. Yomi Services: - If you select to install salt-minion, there should be a drop down box that allow to select the activation key. The needed configuration files (normally done during bootstrap) should then also be created accordingly. Please feel free to contact me if you have more questions or need assistance. I like this way of setting up servers, but we also would need automation in the next step. Thanks Michael Mit freundlichen Grussen / Kind regards i.A. Michael Brookhuis Senior Product Specialist / Technical Team Lead SUSE EMEA Consulting Moersenbroicher Weg 200 40470 D?sseldorf Tel: +491735876783 @: michael.brookhuis at suse.com SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 N?rnberg Germany (HRB 36809, AG N?rnberg) Gesch?ftsf?hrer: Felix Imend?rffer PLEASE NOTE: This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, distribution or other use by anyone else is strictly prohibited. If you are not an intended recipient, please contact the sender and delete all copies. Thank you. On 4/7/20 10:34 AM, Alberto Planas Dominguez wrote: >> Found my mistake. Forgot to enter my IP address in the distro. > > Right, this part is commented in the doc. > > Note that once the node gets provisioned and reboot, you will not have a susemanager.conf that contains the SUMA key as a grain. > > For me is not very clear how to bootstrap a node in SUMA provisioned with Yomi in a clear an easy way, this part is still WIP. If you have feedback, please share! > _______________________________________________ > manager-beta mailing list > manager-beta at lists.suse.com > Check the mailing list archive or Unsubscribe at http://lists.suse.com/mailman/listinfo/manager-beta > From aplanas at suse.com Thu Apr 9 07:51:00 2020 From: aplanas at suse.com (Alberto Planas Dominguez) Date: Thu, 9 Apr 2020 13:51:00 +0000 Subject: [manager-beta] Unable to install system with yomi In-Reply-To: <60e04ff4-6383-cb64-203d-66701b072628@suse.com> References: , <60e04ff4-6383-cb64-203d-66701b072628@suse.com> Message-ID: > I am using the sles15 version. I will receive a pop-up how to register > against SCC but no system will be registered with SALT. I do not get this. You mean the yomi image via PXE boot? If so this pop up was fixed some weeks ago. There is a new jeos-firstboot and a new image with this new version that fix this issue. > Then logging into that server I see that the master has been set to > salt. This means that you have to have a DNS entry for salt. This is in > my opinion a very bad idea. The master should be given with a parameter > during boot. Right. You can change that adding "master=server.example.org" in the kernel command line, during the cobbler registration. For the "salt" default name, I was under the idea that this is the recommended default for SUMA. In any case this is a point that needs be better documented in SUMA, I will add a note to address this. > Configuring the formulas show that there is still a lot to be done. Some > examples: > Yomi Storage: > - when selecting btrfs for /, I would expect that the default > sub-volumes are set automatically. This is not the case. This is a limitation of the formula infrastructure. And I agree. There are a lot of defaults that can be set depending on previous user selections. > - filesystem xfs is not present. And this is mostly used especially for > data volumes. Ahhh good point! I will add this ASAP. > Yomi Software: > - I would expect that I can select software channels that are present in > SUSE Manager. I think we should use what is available as distribution > repositories. They can then be used during installation. Channel is a concept of SUMA? I will take note, as the integration is still very minimal. In this stage Yomi is only the installer, and the pillars are only for the installation part. In this sense is like autoyast today (AFAIK you cannot set SUMA concepts in the autoyast profile) This is an area that I want to extend, separating yomi and yomi-suma states. I will take note for this one. > - If then the channels are selected from within SUSE Manager, it should > be easy to display the available patterns to be installed. This should > be done via checkboxes. AFAIK this is far for what the forms can do today using the declarative YAML file. I will take notes to ask to the right developers about how this can be addressed. > Yomi Services: > - If you select to install salt-minion, there should be a drop down box > that allow to select the activation key. The needed configuration files > (normally done during bootstrap) should then also be created accordingly. This activation key is also a SUMA concept. But I agree, this should be possible to set. This is related with the bootstrap process. Did you try to manually bootstrap the node after the provisioning? If so, did you find problems there? > Please feel free to contact me if you have more questions or need > assistance. I like this way of setting up servers, but we also would > need automation in the next step. Yes please, this is super good feedback. I do not know much about SUMA, and how it is used by an admin. If you see other areas of better integration, please provide the information and I will address them. From aplanas at suse.com Mon Apr 20 06:48:02 2020 From: aplanas at suse.com (Alberto Planas Dominguez) Date: Mon, 20 Apr 2020 12:48:02 +0000 Subject: [manager-beta] Unable to install system with yomi In-Reply-To: References: , <60e04ff4-6383-cb64-203d-66701b072628@suse.com>, Message-ID: From: manager-beta on behalf of Alberto Planas Dominguez Just some updates for the feedback: The jeos-firstboot dialog request for SUSEConnect is not present now in Uyuni nor in Manager:Head >> Then logging into that server I see that the master has been set to >> salt. This means that you have to have a DNS entry for salt. This is in >> my opinion a very bad idea. The master should be given with a parameter >> during boot. > Right. You can change that adding "master=server.example.org" in the kernel > command line, during the cobbler registration. There is a PR that document this use case, there is also documentation in Yomi for this parameter. >> Configuring the formulas show that there is still a lot to be done. Some >> examples: >> Yomi Storage: >> - when selecting btrfs for /, I would expect that the default >> sub-volumes are set automatically. This is not the case. This is not going to be on time for the release. This depends on something bigger, that is the salt classes, or something equivalent. >> - filesystem xfs is not present. And this is mostly used especially for >> data volumes. Done. There is a SR to Uyuni and Manager:Head open with this feature. I will update the status of the rest of the comments when there are changes. From Michael.Brookhuis at suse.com Mon Apr 20 06:59:55 2020 From: Michael.Brookhuis at suse.com (Michael Brookhuis) Date: Mon, 20 Apr 2020 12:59:55 +0000 Subject: [manager-beta] Unable to install system with yomi In-Reply-To: References: <60e04ff4-6383-cb64-203d-66701b072628@suse.com> Message-ID: <92377177-c0c5-7d01-81b0-d32b4a09335f@suse.com> Thanks for the update On 4/20/20 2:48 PM, Alberto Planas Dominguez wrote: > From: manager-beta on behalf of Alberto Planas Dominguez > > Just some updates for the feedback: > > The jeos-firstboot dialog request for SUSEConnect is not present now in Uyuni nor in Manager:Head > >>> Then logging into that server I see that the master has been set to >>> salt. This means that you have to have a DNS entry for salt. This is in >>> my opinion a very bad idea. The master should be given with a parameter >>> during boot. > >> Right. You can change that adding "master=server.example.org" in the kernel >> command line, during the cobbler registration. > > There is a PR that document this use case, there is also documentation in Yomi for this parameter. > >>> Configuring the formulas show that there is still a lot to be done. Some >>> examples: > >>> Yomi Storage: >>> - when selecting btrfs for /, I would expect that the default >>> sub-volumes are set automatically. This is not the case. > > This is not going to be on time for the release. This depends on something bigger, that is the salt classes, or something equivalent. > >>> - filesystem xfs is not present. And this is mostly used especially for >>> data volumes. > > Done. There is a SR to Uyuni and Manager:Head open with this feature. > > I will update the status of the rest of the comments when there are changes. > _______________________________________________ > manager-beta mailing list > manager-beta at lists.suse.com > Check the mailing list archive or Unsubscribe at http://lists.suse.com/mailman/listinfo/manager-beta > From beta-programs at lists.suse.com Fri Apr 24 07:59:20 2020 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Fri, 24 Apr 2020 15:59:20 +0200 Subject: [manager-beta] [ANNOUNCE] SUSE Manager 4.1 Public Beta 3 is out! Message-ID: <5ea2f0b82baea_98373fd250838454767c3@Macbouille.local.mail> We are pretty excited to announce SUSE Manager 4.1 Public Beta 3. As usual, we have prepared tons of updates and we hope you will like it. We also now have a new Public Mailing List[1], so you can share your feedback with our Public Beta Community, our Engineering and our Product Managers. SUSE Manager Beta Page ?[2] Schedule changes Changes to our Beta schedule were needed to adapt to the SLE 15 SP2 Beta schedule changes announced via: SLE 15 SP2 Schedule and Closing the openSUSE Leap Gap[3]. Here is the new schedule of SUSE Manager 4.1: - Beta 2 - March 25th, 2020 - Beta 3 - April 23th, 2020 - Beta 4 - May 22th, 2020 - Release Candidate 1 - June 18th, 2020 - FCS - End of July, 2020 (First Customer Shipment) Requirements and Beta Registration Codes SLES 15 SP2 Public Beta is required as base OS, you can retreive it from here[4]. You will need at least 8 GB of main memory and 100GB of disk space to install the Server and 4 GB of main memory and 100GB of disk space to install the Proxy. Registration is not working with your regular SUSE Manager key, special Beta Registration Code is required!You need to request one via email to beta-programs at lists.suse.com.[5] You only need SUSE Manager 4.1 Beta registration codes for the purpose of installing the SUSE Manager 4.0 Server, Proxy and Retail. No SUSE Linux Enterprise Server registration code is needed. Changes since SUSE Manager 4.0 SUSE Manager 4.1 Beta is based on SLES 15 SP2 Beta! For more details on SLES 15 SP2 Beta, please visit the dedicated sle-beta Web page[6]. If you are looking for the complete list of changes since SUSE Manager 4.0, please check out our Release Notes[7]. Changes since Beta 2 PostgreSQL 12 The database engine has been updated from PostgreSQL 10 to PostgreSQL 12, which brings a number of performance and reliability improvements A detailed changelog is available upstream[8]. To prevent inconsistent configurations and data on upgrade or update, SUSE Manager 4.1 will refuse to start until the database migration from PostgreSQL 10 to PostgreSQL 12 has completed successfully. Automatic database schema migrations and fail-over mechanism Database schema upgrades are now applied automatically during services startup, so there is no need to call spacewalk-schema-upgrade manually. To prevent SUSE Manager services from starting if the schema upgrade has not successfully completed, a fail-over security mechanism has been implemented. More information here[9]. Salt 3000 Salt has been upgraded to the 3000 release for the SUSE Manager Server, Proxy and Client Tools. As part of this upgrade, the cryptography is now managed by the Python-M2Crypto library (which is itself based on the well-known OpenSSL). We intend to regularly upgrade Salt to more recent versions. For more detail about changes in your manually-created Salt states, see the Salt upstream release notes 3000[10]. New documentation guides Two new draft books have been added to the SUSE Manager documentation in version 4.1: - Large Deployments Guide. Everything related to architecture and configuration for large (thousands of clients) deployments is contained in this guide. It contains all the documentation for the SUSE Manager Hub component. Some parts of the Salt guide that dealt with parameter tuning for large deployments have now been moved here too. - Public Cloud QuickStart Guide. This new draft guide shows you the fastest way to get SUSE Manager up and running in a public cloud. It includes instructions for Amazon Web Services, Microsoft Azure, and Google Cloud Engine. These are draft documents, so please provide feedback using the Resources menu in the online documentation. Onboarding of passwordless clients A new SSH private key authentication method, including use of a passphrase on the private key. To protect your security, the private key is only stored on the SUSE Manager Server during the bootstrap procedure and removed immediately after bootstrapping is complete, therefore the private key must be provided for each bootstrap. This is only available from the API in Beta 3. Access to this feature using the WebUI will be available in a future release. Check the Release Notes[11] for an example of how to use the new method. SUSE Manager for Retail: Small stores Where a dedicated SUSE Manager Server or SUSE Manager Retail Branch Server is not feasible, it is now possible to use a Retail Branch Server running in a remote datacenter or public cloud. And more - Monitoring enhancements[12] -- CaaSP dashboards[13] -- Updated Node Exporter[14] - Virtual storage pool support[15] - Proxy visibility in Systems Overview[16] - Improved sync status visibility[17] - RHEL 8 enhancements[18] -- Content Lifecycle Management filters for AppStreams -- Prometheus exporters - SUSE Manager for Retail: SLEPOS 15 SP2 clients[19] Please check out our Release Notes[20] for the complete list of changes. More information SUSE Manager Beta Page ?[20] Release Notes ?[20] Known issues ?[21] We are thankful for your support in trying out our beta products and we welcome your feedback. Have fun beta testing! Your SUSE Manager Team Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Click here to unsubscribe.[22] [1]:http://lists.suse.com/mailman/listinfo/manager-beta [2]:https://www.suse.com/betaprogram/manager-beta [3]:https://www.suse.com/c/sle-15-sp2-schedule-and-closing-th e-opensuse-leap-gap/ [4]:https://www.suse.com/betaprogram/manager-beta/#download [5]:mailto:beta-programs at lists.suse.com?subject=Requesting%20 a%20SUSE%20Manager%204.1%20Beta%20Registration%20Code&body=Re questing%20a%20SUSE%20Manager%204.1%20Beta%20Registration%20C ode [6]:https://www.suse.com/betaprogram/sle-beta/ [7]:https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4.1 / [8]:https://www.postgresql.org/docs/release/12.2/ [9]:https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4.1 /#_automatic_database_schema_migrations_and_fail_over_mechani sm_since_beta_3 [10]:https://docs.saltstack.com/en/latest/topics/releases/300 0.html [11]:https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4. 1/#_onboarding_of_passwordless_clients_since_beta_3 [12]:https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4. 1/#_monitoring_enhancements_since_beta_3 [13]:https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4. 1/#_caasp_dashboards [14]:https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4. 1/#_updated_node_exporter [15]:://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4.1/#_v irtual_storage_pool_support_since_beta_3 [16]:https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4. 1/#_proxy_visibility_in_systems_overview_since_beta_3%20 [17]:://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4.1/#_i mproved_sync_status_visibility_since_beta_3 [18]:https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4. 1/#_rhel_8_enhancements [19]:%20https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER /4.1/#_suse_manager_for_retail [20]:https://www.suse.com/betaprogram/manager-beta/#releaseno tes [21]:https://www.suse.com/betaprogram/manager-beta/#knownissu es [22]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe% 20from%20SUSE%20Manager%20Beta&body=Unsubscribe%20from%20SUSE %20Manager%20Beta -------------- next part -------------- An HTML attachment was scrubbed... URL: