Seite wählen

NETWAYS Blog

Cloud-Ressourcen effizient managen: Terraform Trainer Lennart in der aktuellen iX

Der heute erreichte Grad der Virtualisierung erlaubt es, nahezu ganze Rechenzentren und ihre Netzinfrastruktur virtuell abzubilden. Dazu bedarf es eines Infrastructure-as-Code-Werkzeugs wie Terraform, das sich dem Multicloud-Management verschrieben hat. Terraform stellt Rechenzentrumsressourcen unterschiedlicher Cloud-Provider bereit – bei Bedarf auch für andere Werkzeuge.

Wie das Ganze funktioniert, erklärt unser Terraform Trainer Lennart in der aktuellen iX Ausgabe. Wenn Dich das Thema interessiert und Du vor hast, mit Terraform zu arbeiten, dann solltest Du Dich unbedingt zu einer unserer Terraform Schulungen anmelden. Dein Trainer: Lennart Betz!

Wir haben die Terraform Schulung in drei Versionen im Programm, mit Fokus auf OpenStack, AWS oder Azure. Darum geht’s bei allen dreien: Mit der aktuellen Version von Terraform und seiner Konfigurationssprache HCL (Hashicorp Configuration Language) in Version 0.12 hat sich das Vorgehen zur Automatisierung von Cloud Infrastruktur weiterentwickelt. Unsere Terraform Schulung zeigt, wie Infrastruktur mit der Terraform eigenen DSL (HCL, Hashicorp Configuration Language) idempotent realisiert wird. Neben der Theorie mit vielen Beispielen beinhalten die Fortbildungen praktische Übungen anhand von OpenStack, AWS oder Azure. Ebenfalls erfolgt eine kurze Einführung in cloud-init, um weitere Software zu installieren und zu konfigurieren.

Die kommenden Terraform Schulungstermine

Melde Dich jetzt an und sichere Dir Deinen Platz!

Die genauen Inhalte, Voraussetzungen und alles weitere Wissenwerte erfährst Du auf unserer NETWAYS Trainings-Seite zur Terraform Schulung.

 

stackconf online 2021 | Stretching the Service Mesh Beyond the Clouds

stackconf online 2021 is over and was a full success. It was all about open source infrastructure solutions in the spectrum of continuous integration, container, hybrid and cloud technologies. We’re still excited about all of our experts sessions and the large number of participants who joined us from all over the world. In the following you get an insight about one of our talks.

At stackconf online 2021 Rosemary Wang was with us, and she had a great topic on how to extend a service network beyond clouds. At the beginning she told us about her work at an organization, where different environments were used. These environments were running applications, some in AWS, data centres, Kubernetes, virtual machines, or Azure. The last thing that is missing is a way to control everything from one point.

So, what is needed is an infrastructure layer and an automation that controls the infrastructure layer. The combination of these is a service mesh. She showed us a solution with a Consul cluster, which is used in the datacenter and in the cloud.

This means that everything that is service to service goes through the proxies first. For example, in the data centre, the UI goes through the proxies to communicate with the application. Consul takes care of the configuration of the proxies and controls the rules and placement of where traffic is allowed to go within the environment.

The UI can also use the proxies to reach the application in the cloud. This allows cross cloud access. But aren’t there more problems with a service mesh? The answer is yes, you do have certain issues that you need to address, but you need to consider whether or not to avoid the service mesh. If you do not use a service mesh you end up with little automation and multiple checkpoints for the environments.

Several Types of Topologies

To get back on topic, we won’t try to get the service mesh across all environments, but Rosmary would like to show us the several types of topologies you have.

First, the service mesh is deployed in the cloud and then a network automation piece is added to synchronize. The benefits in the service mesh are controlled retries and error handling to non-service mesh and progressive delivery techniques such as canary, A/B testing and feature flagging. On the other hand, we have the benefits in the non-service mesh like automated control and no change to existing applications.

Let’s move on. After deploying the service mesh in the cloud, you deploy an ingress gateway that helps control traffic from the ingress to the cluster. The information it receives is transmitted to a Consul Terraform Sync, which configures the application load balancer.

How Consul Terraform Sync Works

Here Rosmary explains the advantages and disadvantages as well as how Consul Terraform Sync works. Afterwards there was a demo of how everything works together.
On the whole, I can say that Rosmary’s talk was very successful. I was able to learn a lot about the topic myself, even though I didn’t know a lot about it before. I hope the talk can convince you as much as it convinced me.

I could go on explaining in detail what Rosmary mentioned in her talk, but I would like to leave you with this.
If you want to learn more about the talk you can watch it in full length, I really recommend it.

Full talk and more from and about stackconf

Watch the the whole talk by Rosemary Wang:

YouTube player

 

stackconf 2022 will take place in Berlin. The final date will be announced soon. If you want to learn more about infrastructure solutions in advance you have the possibility to take look at our archive where you can find all slides and videos from this year’s stackconf.

Stay tuned!

Joshua Hartmann
Joshua Hartmann
Systems Engineer

Joshua hat im Sommer 2023 seine Ausbildung zum Fachinformatiker für Systemintegration bei den NETWAYS Web Services erfolgreich abgeschlossen. Heute ist er ein wichtiger Teil des Teams, das sich mit großer Hingabe um die Kundenbetreuung und die kontinuierliche Weiterentwicklung der SaaS-Apps kümmert. Neben seinem musikalischen Talent am Klavier hat Joshua eine Leidenschaft für Wintersport und findet auch Freude im Gaming. Doch am allerliebsten verbringt er seine Zeit mit seiner besseren Hälfte, denn sie ist für ihn das größte Glück.

How To NWS: Infrastructure as a Service mit OpenStack

Im letzten Blog habe ich mit unserer Software as a Service Plattform den ersten Teil unseres Portfolios vorgestellt. Hier kann sich jeder standardisierte Apps schnell und einfach selber anstarten. Manchmal lassen sich die Anforderungen unserer Kunden aber nicht über die Apps abdecken, da beispielsweise per Default deaktivierte Funktionen benötigt werden oder wir schlichtweg den benötigten Dienst nicht in unserem App-Portfolio haben. Wer individuelle Anforderungen an seine IT Umgebung hat, der ist in unserem Infrastructure as a Service Bereich richtig.

Abhängig davon ob virtuelle Maschinen oder Container zu orchestrieren sind, können sich unsere Kunden zwischen OpenStack und Kubernetes entscheiden.

In dem heutigen Blog möchte ich unser OpenStack Angebot vorstellen:

Bei OpenStack handelt es sich um ein OpenSource-Projekt, das von zahlreichen namenhaften Unternehmen (Suse, Linux, HP etc.) unterstützt und ständig weiterentwickelt wird. Ursprünglich ins Leben gerufen wurde es von Rackspace und der NASA. Es setzt sich aus einzelnen Softwareelementen (Nova, Keystone, Glance, Neutron, Cinder, Swift, Horizon) zusammen, mit denen man im Verbund eine Cloud-Plattform erstellt.  Es handelt sich also um ein Cloud-Betriebssystem mit einer Vielzahl an Funktionen. Eine wesentliche Voraussetzung für das Cloud-Computing ist die Virtualisierung, das heißt die Trennung der Stack-Ebenen. Das ermöglicht, dass mehrere Betriebssystem-Instanzen auf der selben Hardwareeinheit betrieben werden können. Auch der Zugang zu Speicher und Netzwerken wird virtualisiert. Im Endeffekt können so sämtliche Bausteine eines Rechners durch Schnittstellen und Konfigurationen referenziert werden. Man erhält eine flexibel änderbare und skalierbare Struktur.

Dadurch, dass OpenStack von Cloud-Computing-Experten aus aller Welt – also großen Konzernen (z.B. Telekom), mittelständischen Unternehmen (wie uns) und kleinen, hippen Startups – genutzt und ständig weiterentwickelt wird, bleibt gewährleistet, dass das Projekt ständig auf der Höhe der Zeit und den Ansprüchen des Marktes gewachsen ist. Ein weiterer, großer Vorteil gegenüber den großen, bekannten Cloud-Anbietern ist der Wegfall des Vendor Lock-in. Es sind ausschließlich standardisierte Schnittstellen im Einsatz. So kannst Du bei Bedarf Deine Unternehmensdaten unkompliziert migrieren, was einen Anbieterwechsel jederzeit möglich macht.

Mit unserem OpenStack kannst du Server und Netzwerke schnell und einfach starten. Virtuelle Maschinen, Speicher und Netzwerke lassen sich mühelos einrichten und vor allem auch jederzeit dynamisch an sich verändernde Anforderungen anpassen. Dabei kann bei den Virtuellen Maschinen aus einem Pool von vorgefertigten Images für alle gängigen Betriebssysteme mit unterschiedlichen Sizing-Varianten gewählt werden. Diese lassen sich ganz einfach per Knopfdruck starten. Sollte das gewünschte Sizing nicht dabei sein, kann man sich die Ausstattung der VM selbstverständlich auch individuell nach seinen Vorstellungen anlegen. In Puncto Sicherheit kann man mit Methoden wie Firewalls, Verschlüsselung und Dienstrichtlinien festlegen, wer wie auf welchen Server zugreifen kann und beim Thema Backup kann man frei entscheiden, ob Snaphots oder Images in welcher, freiwählbaren Rotation gesichert werden sollen. Alle Daten liegen 3-fach redundant gesichert auf unseren Ceph-Cluster, der sich über unsere beiden DIN ISO 27001 zertifizierten Rechenzentren verteilt.

So lässt sich das OpenStack Projekt bequem und übersichtlich über unser Dashboard zusammenstellen und einrichten. Der Punkt der Übersichtlichkeit führt mich auch gleich zu einem weiteren wichtigen Vorteil unseres OpenStack Angebots: Bezüglich der Kosten können wir ein maximales Maß an Transparenz bereitstellen. Es gibt keine undurchsichtigen Pauschalen und Gesamtpakete. Alle verwendeten Ressourcen werden stundengenau abgerechnet. Über unseren Cost Explorer siehst Du die für den Monat bereits entstanden Kosten und bekommst anhand der aktuell genutzten Ressourcen auch gleich eine Hochrechnung über die voraussichtliche Summe am Monatsende. Man hat die Kosten also zu jeder Zeit im Blick und  kann im Bedarfsfall sofort reagieren. Das liegt auch daran, dass es keinerlei Vertragslaufzeiten gibt. Wird eine VM nicht mehr benötigt, kann man diese umgehend runterfahren. Am Monatsende zahlst Du dann nur den Betrag, der bis zu der Abschaltung entstanden ist. Das gibt Dir absolute Flexibilität in beide Richtungen – Du kannst schnell wachsen und, wenn nötig, Dein Setup auch direkt verkleinern.

Und natürlich haben wir auch hier technische Unterstützung im Angebot. All diejenigen, die ihre Zeit nicht mit der Einrichtung und Wartung ihrer IT-Infrastruktur verbringen wollen, können unseren MyEngineer-Service dazu buchen. Auf diesen werde ich aber erst in dem übernächsten Blogartikel genauer eingehen.

Hier geht es zu unserer OpenStack Seite: https://nws.netways.de/de/cloud/

Hier findest du unsere Preisliste: https://nws.netways.de/de/preise/

Und hier findest Du Tutorials und Webinare zu OpenStack: https://nws.netways.de/de/

Stefan Schneider
Stefan Schneider
Account Manager

Vor seiner Zeit bei NETWAYS hat Stefan als Projektmanager in einer Nürnberger Agentur dabei geholfen, Werbeprojekte auf die Straße zu bringen. Seit Juni 2017 ist er nun stolzes Mitglied der NETWAYS-Crew. Hier war er zuerst der Ansprechpartner für unserer Schulungen und kümmert sich aktuell um alle Anfragen rund um unser Hostingangebot. Die Freizeit vertreibt sich Stefan am liebsten mit Sport. Vom Joggen über Slacklining bis zum PennyBoard fahren ist er für alles zu haben.

stackconf wrap up – DAY 1

stackconf is back and better than ever! Today started off very strong with a few new additions and great speakers that gave us an insight to a variety of topics.

This being my first year at the conference, it was very exciting to get to started and involved with all the action and flow of all of the people coming together to learn something new. Right from the get go, you can see the amount of work that the Events Team put into making stackconf happen and the fact that it is all done online is really quite impressive. Of course we had the event online last year, but you can really see that this year has really been refined and delivered to a very high quality.

We’ve had a stackconf cake!

Before the conference had even started, people had already started communicating in the Rocket.chat channel and this year they also had the opportunity to be „present“ at the event. This year we made our own conference in the form of Work Adventure! This gave people the chance to walk around with their character and interact with people as if they were really there! This gave everyone the chance to be able to „meet“ with other people at the conference and have their very own chats with one another. The ones that didn‘t want to talk right away were busy sprinting around the conference area (me being one of them…).

We had a great kick-off from Bernd and Christian, who were both looking very smart and ready to guide us through the first day of stackconf!

Spot the Antipattern and the IKEA effect

Jumping into the first talk of the day Arushi Jain from Reddit kicked things off with her topic on Spot the Antipattern. Arushi showed us how to spot an Antipattern, why they exist and what we can do to help identify and avoid such patterns. This was also a very honest topic as Arushi went through some of the problems Reddit faced themselves and the systems they were using. She also talked about the use of certain methods and how sometimes they can be falsely used in lots of other applications instead of the ones they are meant for. An interesting point I picked up was the IKEA effect, where people that have made something themselves they have a hard time letting go and this was a very good comparison to code and current workplaces practices.

Katja tweeting.

Looking into our second talk, we’re greeted by Ara Pulido as she showed us Policy as code in Kubernetes with OPA and Kubernetes. This was another interesting topic and for those of you who are up to date with K8s, you would have found this talk very informative. Ara showed how some policy rules can be implemented to Gatekeeper so that pods can only be launched once they have reached a specific set of criteria. This can help avoid a wrong deployment and keep everything organised and working together. We got a quick look at the OPA Ecosystem, some constraint templates and a short demo on auditing pods to check to see if they are performing as planned.

We were gracefully transitioned through the talks by Bernd and Christian, who kept us chatting and talking in the channels whilst keeping the pace with all of the talks that went on today. Great job lads!

From Peter Elmer’s talk.

Our next speaker Peter Elmer came by with a very interesting topic about Data Driven Security. This gave us an insight into machine learning and how they incorporate data to make their programs „smarter“. Peter went into more detail as to how logic is created from data and turning decisions from a probabilistic factor to a more determining one. He also looked at how we can prevent attacking by defending at the source. This is a hot topic at the moment and also one to watch for the future.

Pragmatic application migration

Our next topic came from Nicolas Fränkel and he talked about Pragmatic application migration to the cloud with Quarkus, Kotlin, Hazelcast and GraalVM. Nicolas gave us some points as to why using the cloud is such a great idea and the benefits of doing so. He then went onto explain the different methods used when transitioning to the cloud and the drawbacks of having to rewrite everything from scratch. Alternatively, the use of JVM although it has a slow start up time, can be run once everywhere and adapts to the current workload. At the end Nicolas gave us a quick demo on a URL shortener, very cool!

Yummmm: stackconf and icescream!

To help break up the pace after lunch, we had two Ignites which were quick snippets of two very interesting presentations from Lawrence Finn and Tadeh Hakopian.

Lawrence talked to us about a cloud-sidecar application which sits next to your application and speaks to cloud services for you. The application even thinks it‘s talking directly to the cloud services!

More training methods are always better

Tadeh Hakopian then came by and talked to us about the importance of visuals when teaching code and reducing bias. Tadeh helps explain that removing barriers and using visuals helps make the first steps of developing easier and less scary when starting out. We have all been there before and looked at code thinking that it is something from The Matrix. Another good point he mentioned was that more training methods are always better, which is true as not everybody learns the same and this opens up a lot of opportunity for people that think differently. These methods help people build better room designs for example or build buildings more efficiently.

From Ricardo Castro’s talk.

Getting back on track with our talks, Ricardo Castro enlightened us with GitOps: yea or nay? Ricardo showed the advantages of using GitOps like enhanced productivity, stability and reliability.

He also went into the usefulness of rollback with applications as it is on the same basis of git we are all used to. The idea is to have a lot of it automated and out of the box integration. We then got the chance to see it in action with a demo of flux deploying an application and showing us how it pulls the information needed to work.

The scaler is very clever

Sebastian, Head of NWS, at stackconf.

Our next talk came from Bram Vogelaar and his topic on Autoscaling with HashiCorp Nomad. Bram gave us a brief look at how scaling was done in the past and how it has proceeded up until now. The great thing with Nomad is that is follows a very simple procedure, Keep It Simple Stupid. He showed us how easily the code is written and how the autoscaler works based on checks. The scaler is very clever as it is able to swell in order to keep up with demand, so you never run out of resources, and reduce them again so they aren’t being wasted.

Diego Ciangottini was up next to talk about Setup Min.io and Open Policy Agent for a multi purpose scientific platform. Diego brought up the demand for computing resources for the INFN communities, that are based all over Italy and their need to be able to obtain these resources. This very interesting and complex project looks at various computing challenges for data storage for multiple communities and the sustainable reuse of data. He then gave us a quick look at the solutions and user management with MINIO.

Our stackconf organizers Markus and Lukas.

Our next speaker was Matt Jarvis with a talk about the importance of Continuous Security – integrating security into your pipelines. Matt explained how the line between the roles of developers and security is increasingly getting blurred and how there is a need to bring the security checks to a developers level and the tools needed to do so. Of course this means a greater responsibility, which is why Snyk is there to help the Devs when checking their Pipelines a whole lot easier. Matt also went over some current flaws with current images and containers and then showed us how they could be checked and corrected by Snyk. Another great topic from our speakers.

We accidentally created a cloud

Great job, moderators!

Our last awesome speaker of the day was JJ Asghar and his very interesting topic, We accidentally created a Cloud on our IBM Cloud. JJ starts off with how everything started with ‚for loops‘ on bash and the problems they faced and how they moved on to learning and using python scripts instead. Now as things have improved JJ explained the use of AWX and using Ansible playbooks to help run the code for you. With the help of their kubeadmin IBM are able to control a multitude of clusters all at once.

Although people may have been a little shy on the first day, which is understandable, the general atmosphere and communication from everyone was fantastic. We had a strong start to stackconf and we have a great feeling for more on what is to come. Our guests and speakers will have plenty of opportunities to mingle with other tech-heads and ask plenty of questions in the coming days. Keep up to date with everything that is going on and come and join the fun, it‘s free!

Jitsi Customization

Custom Branding

A few months have passed since our last Jitsi features blogpost and seeing as the demand for Jitsi is still high, we are permanently looking for ways to improve our Jitsi for our customers. Therefore, I would now like to show you the new features which are currently in production.

Lately we got more and more requests for a custom branding of Jitsi. Because Jitsi does not offer such an option, we took the matter into our own hands and created a possibility that you can configure Jitsi yourself.
Many Jitsi users don’t want to have their setup with the default design. They instead want to add their own look. If you have ever searched for custom branding for Jitsi, you will quickly find out that there are already some community contributions available. This is good for the users who run their own jitsi. But for customers who rely on a service provider soon realise that these options are often not represented. Some service providers offer the possibility to create a custom setup for the customer, but such projects are usually associated with higher costs and a lot of hassle.
Therefore, we want to offer the possibility that everyone can easily configure their Jitsi on our website and finally get what they want. The watermark logo, the background and the colour scheme can be customized as desired.

Custom Domain

Apart from the appearance, we are currently also missing the option of the custom domain, but the wait will soon be over. What is also currently in demand is the possibility to have your own domain. This is unfortunately not currently possible with the current setup. But with the new structure of Jitsi, this will no longer be a problem.

JWT Authentication

If we now go a bit further in the direction of security, we come across another important point that is currently being worked on. The selection of the Jitsi authentication. Here we have also put together and provided something magical for you. As standard we have the authentication with user and password, but after our update you will have the ability to choose between standard and JWT authentication.

So it will soon be possible to configure everything on your own.
For these features we will also provide a technical blogpost, where we will explain step by step how all these configurations are implemented in Jitsi.
I hope I could peak your interest with this blogpost. If so, then you are as full of excitement as I am, because these features will be awesome.

If you are still not sure if you want to use Jitsi, check out our blog comparison of Jitsi vs Zoom vs BigBlueButton.

Joshua Hartmann
Joshua Hartmann
Systems Engineer

Joshua hat im Sommer 2023 seine Ausbildung zum Fachinformatiker für Systemintegration bei den NETWAYS Web Services erfolgreich abgeschlossen. Heute ist er ein wichtiger Teil des Teams, das sich mit großer Hingabe um die Kundenbetreuung und die kontinuierliche Weiterentwicklung der SaaS-Apps kümmert. Neben seinem musikalischen Talent am Klavier hat Joshua eine Leidenschaft für Wintersport und findet auch Freude im Gaming. Doch am allerliebsten verbringt er seine Zeit mit seiner besseren Hälfte, denn sie ist für ihn das größte Glück.