Project Bicep? Biceps? Do you mean like bicep curls? Muscles? What does this have to do with ARM or ARM templates? Well, to master ARM templates, we can use a little extra power. So, It’s a joke so bad it’s good as Microsoft’s Alex Frankel put it.
Over the years, I have noticed a couple of challenges when it comes to Infrastructure as Code (IaC). It is not an easy thing to achieve in practice. Not only in the cloud but anywhere. It is a significant hurdle in achieving IaC. Maybe you have the same experiences.
Azure Infrastructure as Code
In Azure, one of the biggest challenges has been the learning curve when it comes to writing the JSON. JSON, the “human-readable” data interchange format that brings ARM and ARM templates to live. It isn’t something you pick up super quickly and turns out to be harder and harder to use when things become more complex and diverse.
Other challenges are related to managing the templates, getting pipelines set up reliably and consistently for all resources in Azure tenants, subscriptions, resource groups, etc. It is not something that I would call inviting and easy to do.
Then there are the real-world realities we need to handle. There is a ton of “stuff” out there where deployment, configuration, orchestration, and change happens in different ways. How does one onboard all that in an IaC process without too much risk of breaking things? Unfortunately, this is tedious and fragile.
We like Infrastructure as Code
For many people, the above is a bit discouraging. Don’t get me wrong. People see, understand, and like the idea of Infrastructure as Code. They just have a hard time getting there. There are all sorts of tools for various environments and needs. We have all at least heard and probably looked at Chef, Ansible, Puppet, or Terraform. There are many others still, but I just listed the ones that have been getting some serious attention over the last four years. Choosing one is losing the benefits of another. Using them all is an operational, skills, and management challenge. They all have their strengths and weaknesses. The main differences are whether they take a procedural, declarative, or an orchestral approach to getting the job done.
While orchestration is very popular, it does feel a bit like a failure, but that is “emotion”. Why? Well, because in the end, we cannot manage change very well and end up throwing everything away and replacing it with a new deployment that has the changes in there. Everything is a cow now that gets slaughtered and replaced when it doesn’t function as expected or needs to change. That works well for lightweight and fast implementations. It is somewhat painful when using this in more massive deployments. But still, when looking at the results and preventing configuration drift, it gets the job done.
But even the best tools have issues that can be best described as “death by a thousand cuts.” The concept is simple, but that doesn’t make it easy to do!
Microsoft has heard this feedback
We like Infrastructure as Code. We do find it too hard to do well, especially if that is not the bulk of your work, and you are not a guru at it like Stanislav Zhelyazkov.
When Microsoft asked on Twitter, “What do you think is a knowledge gap for traditional #ITPros when it comes to transitioning to the cloud” I replied, “The biggest skills hurdle is related to IaC. ARM is tedious and hard to learn for many, yet a cornerstone … Fix that, and we can move 10 faster in any cloud journey.”.
The above is not new feedback, far from. But recently (Build 2020) they talked publically about what they are doing about it if I recall correctly. Yes, Microsoft is addressing this challenge. Just last week I saw Project Bicep go public on Github!
So what is project Bicep?
Bicep is a project Microsoft announced at Build 2020 (May). It delivers what Microsoft calls Transparent Abstraction over Azure ARM and ARM templates. ARM ==> Bicep get the joke? Ok, never mind, it is terrible to search for, however. You get a lot of irrelevant hits.
It has a couple of goals as you can learn from the video.
Human friendly, so readability and comprehensibility are essential. You have to be able to understand what you read and write without much effort.
What you write will create or compile JSON for you. Microsoft now seems to like “Transpiles” for this. Where earlier the sort of made the analogy of JSON being some sort of the Intermediate Language (IL) of IaC.
If you think of JSON of an IL (as MSFT suggests), it is easy to see that, just like with .NET, you might see different languages use to achieve the same goal. But for now, that is not the goal. The goal is to get a working, functional declarative language that is suitable for all kinds of users. We’ll see where this ends up.
It focuses on modularity, so no, it will not create giant ARM templates, but modular ones. That means there is multi-file support.
It should evolve at the speed of Azure, so no waiting for six months to get new functionality implemented. Microsoft calls this “transparent abstraction.”
They plan a migration/conversion/export tool for existing ARM JSON!
Read up on project Bicep over here https://github.com/Azure/bicep. It clarifies the current state of what Bicep is and is not. I hope this moves fast and delivers better tooling to make Infrastructure as Code a better, more accessible, and more achievable goal for all of us.
Bicep is at a super early stage of its existence. This is the earliest Alpha you can imagine. It is going to break, barf, and probably puke on your Azure stuff once in a while. So please,DO NOT USE THIS IN PRODUCTION. Right now it is only to get a feel for it, tinker around and get some feedback. This is you only and final warning.
In all honesty, it is very raw and as a (non-Linux) hardcore dev, this is not love at first sight for me, as I had hoped to use PowerShell for this. I hope it will mature and I will grow to love it and like using it much more than ARM. Anyway, dive into the bicep tutorial to see what you think.
Boring as it might be, reading your End User License Agreements can be useful. That is no different for the Veeam Community Editions and the Veeam EULA. The EULA came up recently when discussing Veeam services an IT Service business can offer to its clients.
It includes support for up to 10 Instance licenses and allows you to protect any combination of physical machines, virtual machines, and cloud workloads for free. You get the standard edition backup functionality. Veeam also offers community editions of Veeam ONE™ and Veeam Backup for Microsoft Office 365. Cool!
The value for you
This is an awesome offering. It helps people with small environments and small budgets out big time. They get top-notch data protection for free, Not just that, they get all the goodness of the well known Veeam data portability, ease of recovery, reliability, and support. Then there are the forums, where you’ll find many helpful and skilled eyes. It is a very active community.
The value for Veeam
First of all, Veeam is smart. They put their products into as many hands as possible. When that happens people get to use, learn, know, and love the products. That leads to sales when 10 instances just don’t cut it anymore. It also leads to a lot of feedback and insights. A lot of the people using it are early adopters and IT professionals. This means that they use the products and if they find issues Veeam gets telemetry and early insights to potential bugs. This helps them deal with then proactively before the big enterprises upgrade as that usually takes a bit longer.
Secondly, Veeam is community-minded. And that is not just lip service, they act on it. I know this first hand and you will to when you experience it. The community editions of their products are just one example of that.
As mentioned, you get support. Within reason, just like with paid support the Veeam support engineers will not do implementations for you. So just doing “click, click next” like a baffling buffoon won’t get you far. Support is not meant to replace your own skills or provide free IT designs and implementations. That work is for you. The support with the community editions is about finding and fixing issues with the product. That’s very valuable for Veeam as early adopters who run into issues help surface those in time to address for the slower moving customers.
Do It Yourself
The Veeam Community Editions EULA boils down to the fact that it is a Do It Yourself (DIY) arrangement.
As a hobbyist, student, enthusiast, employee who wants to learn more about Veeam products or leverage them to protect a company or non-profit workloads you can do that up to the 10 free licenses. It is perfectly legal to do so. But as it is DIY, you cannot hire someone to do this for you. Likewise as an IT consultant. contractor or freelancer, solo or with a company, you cannot offer paid services around Community Edition. For that, they have different licensing options. You can read up on this in the EULA.
The rules around Veeam Backup & Replication Community Edition are simple. As an end-user (hobbyist, employee, business) you get most of the famous Veeam capabilities and benefits for free up to 10 instances. Yes, you can use this in production and you get free basic support from Veeam. Then there are the forums, which offer a wealth of insights and where many helpful eyes can assist you. For this to be legal you have to implement and maintain the community editions yourself. You cannot hire people to do it for you. As an IT service company, no matter what the size or nature, you cannot offer commercial services and build a business model around the Veeam Community Editions. That’s what the commercial versions and partnerships are for. As far as EULA’s go, that is crystal clear.
Last week, around August 26-27th 2020 Custom Route Tables in Azure Virtual WAN lit up in my Azure Tenants. Awesome news. Normally this should have happened the week of the 3d of August 2020. However, some delay happened. Now it is here is has come in silence. Which I find odd. This is a major capability that offers so much of what we need to make Azure Virtual WAN shine. But it is here, ready to shine at Microsoft Ignite
Custom Route Tables in Azure Virtual WAN
What do we have now? You can read up on Azure Virtual WAN route tables over here. I have made a video about all this which you can find on my blog and on my Vimeo channel. Please take a look for some walkthroughs and links to some other blog posts by me on Azure Virtual WAN.
First of all, let’s discuss the labels. Labels logically group route tables. These are very helpful when propagating routes from connections to multiple route tables. The Default Route Table has a built-in label called ‘Default’. When you propagate connection routes to the ‘Default’ label, it automatically applies to all the Default Route Tables across every hub in the Virtual WAN.
Now, we can discuss associations. Each connection is associated with one route table. This means that the connection can send to the destination indicated as routes in the route table it is associated with. The routing configuration of the connection will show the associated route table. This is very important for connected VNETs. Multiple connections can be associated with the same route table. Note that all VPN, ExpressRoute, and User VPN connections are associated with the same (default) route table.
By default, all connections are associated with the Default route table in a virtual hub. Each virtual hub has its own Default route table. You can add one or more static routes to the default Route table. Static routes take precedence over dynamically learned routes for the same prefixes.
Last but not least, connections dynamically propagate routes to one or more route table. VPN, ExpressRoute, and User VPN connections propagate routes to the same set of route tables. With connections like a Site-2-Site VPN, Express Route, or Point-2-Site VPN, routes are propagated from the virtual hub to the on-premises router using BGP.
A “None” route table is also available for each virtual hub. Propagating to the None route table implies that no routes are propagated from the connection.
Some need to ask
Finally, some customers need to reach out to support in order to get Azure Virtual WAN Custom route tables to light up.
As a result, I suggest you do so to start kicking the tires and then dive in deeper. This is a cornerstone technology for Azure networking going forward.
I have not found any documentation or guidance in regards to automation with PowerShell, Azure CLI, or ARM templates yet. I expect this to be forthcoming as this is much needed. As a result, I hope we’ll see this by Microsft Ignite 2020.
Azure Virtual WAN with the secured Virtual Hub and custom route tables offers the capabilities we have been waiting for. With these capabilities in place. Azure Virtual WAN is the future of Azure virtual networking. Therefore, I fully expect to hear a lot more about it during Microsoft Ignite in September. I personally will focus on this part of networking in the coming months. It is a stock part of any Azure initiative and project in the near future.
By now most businesses and other organizations will have woken up to a, for many of them, new reality. The reality that the office is a relic of the past. Not completely and in all situations, but for many people, use cases and industries. The writing has been on the wall for quite a while, that is for sure. But now it is being driven home remorselessly. Corona and Covid-19 are just messengers.
If you make your living selling office spaces this is bad news and you are likely to disagree with a vengeance. Join the club of transport and other companies. Change can hurt when you are at the receiving end. Relics or not, offices still have their use, but their dominance is over and it has been for a while.
Corona & Covid-19
At the time of writing, it’s been about 6 months since, all over the globe, we went to a “work from home as much as possible” approach. This in order to deal with the impact of Corona and Covid-19. While we are all telecommuting, our businesses are still running and they function just fine. Better than if we would require everyone to be in harm’s way during a global pandemic, That should make everyone think.
Some say this is only possible due to technical advances in the past 5 years. I think they mean Teams and Zoom. But in reality, it has been possible for well over a decade. At least where I had a say in the infrastructure.
Working from home has its challenges for sure. Things can be better technically for some of us. But hey considering this was all done under the pressure of Covid-19 and despite some managers, it’s not too bad. For many, the home office can use a second screen and or better chair. People with kids, who are caretakers of elderly dependents, etc. will have some extra challenges. Quite often the home office could also with a makeover and some improvements to handle hot or cold weather better and to make permanent telecommuting more comfortable.
The mere fact that some work at the dinner table demonstrates the need for a home office in the first place. Blame short term thinking and acting as if nothing ever changes for this when it comes to housing and public domain planning. But all that does not distract from the fact that businesses keep running during the pandemic. As a matter of fact, they are running well.
Business as usual
Many of my buddies in IT and I have been working from home part-time or full time for well over a decade. We did not miss a beat. Bar the pandemic specific unpleasantries it was almost business as usual for us. Lucky we.
My home office and lab is very well equipped. At my own expense. I value telecommuting and it shows. Actually, the topic comes up every now and then amongst us to just pack up and live wherever you want while working. Life is short and it might be over before you ever retire. So make the most of it.
The one thing to avoid is that working from home turns into living at work. That’s when you have lost balance. However, that is no excuse to haul half of the population back and forth to offices every day.
Business is about money
As businesses and other organizations come to terms with that new reality they also have to face another fact. The fact that the total cost to keep someone at a desk in a building (rent, power, heating, security, insurance, regulations, catering, …) is high. In many cases too high. And as the workforce has been working from home for almost 6 months now they should be questioning why and to what purpose that money is spent.
If you excel at dynamic operational management you should already be making plans and reducing your costs by reducing office space, if not downright abandoning it. Even if organizations need to spend 150$ or more per month per employee on home office expenses they will still come out ahead. And not just the businesses, also society as a whole as well as the individuals involved. The tools, the technology we need exists and are only getting better. Regulations might need to catch up, but again, that is no reason to keep offices around.
While some employees struggle with 100% telecommuting, especially combined with the stress induced by a global pandemic, many have woken up to the many benefits as well. They realize they can reduce commuting costs (gas, public transport), dry cleaning, work attire, commute time, etc… Next to that, they, if are not too challenged by the pandemic’s extra burdens, might very well notice they can get their work one more productively and undisturbed compared to when in the office merry go around. This can lead to a better work-life balance and time regained.
More than ever before, people will demand to work from home. Governments and business planning for the next crisis will want this to succeed as well to soften the impact and smoothen the experience of a pandemic or other disaster. All that while saving money and reducing congestion. What’s not to like? The number of work from home job adds has risen with 300%. Smart businesses are leveraging work from home to attract top talent. Others are losing talent over it. Think about that.
Make no mistake, the moment you become more productive businesses will try and recuperate that time for their own profit and out need. No need to be naïve here. The race to stay competitive will push them to do so, that, along with greed. Let’s face it, most innovations that offer benefits to the average person soon become revenue or cost avoidance streams for others. Look at solar panels and smart meters. Right now they are being used to protect revenue streams of providers and favor higher consumption. By the same reasoning, we might have to pay for the empty office buildings. The risk of an entrepreneur is often socialized while the profits are private. In those cases, you don’t hear them complain about entitlement.
Time for managers to lead by example
Managers will have to step up. They need to learn how to really hire and lead talented people. That is a different ball game than just collecting employees into open office spaces and having them run around to meetings all day long. It is as if the entire technical evolution of the past 25 years has passed management by when you see how often this is still the reality for many of us. So maybe it is not just offices that are a relic of the past.
Let’s get the obvious remark about jobs that require a physical presence off the table. Yes, they exist, there are many of those. Those people can also benefit from the mere fact that the rest of us are not moving around like zombies every morning and evening without any good reason. Especially since working at an office has at best very little, likely no positive and quite possibly a negative impact on getting the job done.
Backpressure is inevitable
The incumbents, comfortable in the predictability of the status quo, will always challenge change. They only like change when others “that are stuck in their ways” have to deal with it or when it benefits them significantly. In any other situation, they will fake change when required, but that’s about it.
When you are in the business of facility management the idea that the office is a relic of the past will cause some disconcert. No matter how you translate or communicate that message, the consequence is that the facility business is about to shrink significantly. And with that comes the loss of power, money, and prestige.
Reducing or abandoning offices all to getter happens for good reasons, actually. Office space is very expensive and not that efficient let alone effective as many assume. Offices tend to lead to wasted time, groupthink and can be distractive to the point it diminishes productivity.
Many will be tempted to fill those offices again as soon as possible. Why? Because they own real estate or have investments in sales and leaseback or even pure long term leases. They’d rather throw good money after sunk costs to avoid looking like they should have rethought the entire office n the 21st-century thing a bit earlier. A few decades earlier even. But instead, they have been running after the “latest” office fashions like cubicles, open office plans. Often a decade too late, when the fad had been debunked a 100th times already. All this while technological progress was showing us all the way forward.
You will see lobbying and fear mongering to get people back into offices and some politicians will fall for it. But work and offices are no longer as connected as they use to be. As long as the money flows into their pockets they will not call something a waste. Despite the costs to others and the environment.
I am an IT professional who is active in the global community. The majority of interactions and collaboration happens online, across time zones even. We work, learn, collaborate remotely together. Consequently I can only shake my head at so much institutionalized inertia.
Offices were devised many centuries ago out of necessity
Offices were devised in an era that administration and bureaucracy and complexity with global operations were growing. Meeting the needs to address all that required the office to be invented. Read https://www.bbc.com/news/magazine-23372401. Even back then many employees experienced unhappy and unsatisfied excuses for “careers” in those offices. So yes offices can go away or be reduced significantly. That is okay. The same happened with cowboy bunkhouses, factory housing, horse and carriage as well as steam engines, and now even combustion engines.
The need for offices has diminished significantly by now. Many are remnants of a bygone era. When not strictly needed, they exist to keep a market alive and prevent real change hat would upset the powers that be. Blame, or rather thank information technology.
Some offices are needed, many are not
I am sure offices will be adapted to be more corona (pandemic) proof, and while needed, it does not make office life more enjoyable. People will be hesitant to return to dense landscape offices and overcrowded meeting rooms that are used by another bunch of people every hour or half-hour. The commute, the distractions, the cost will all be balanced against the benefits. Offices will lose that comparison. Sure when people really need a job, they might put up with having to go to an office, but that is not a choice. Given a choice, well over half of the employees will prefer to telecommute at least part-time.
If a job requires you to be in an office and you cannot find candidates it means that what you offer is just not good enough and the need to be there is not very convincing. Why would I put up with landscape offices that cause me stress, reduce my productivity as they kill my ability to concentrate? On top of this, to add insult to injury it makes lose time in stressful commutes, money on travel, etc. To make it even worse it wrecks my ability to balance that with the needs of children or elderly under my care and makes shopping race against the clock.
Commuting adds to traffic congestion, pollution, and stress. So when the jobs are equal, as most are, with only a minor variance in pay, why would I choose a job that imposes all that on me over one that doesn’t? What is in it for me and your company? Catering to failed leadership in the face of clear and present alternatives?
I will no take jobs that require my presence in the office full time unless I absolutely had to. So while many complain about not finding talent and secretly hope a bit more unemployment would make finding candidates easier maybe they should address their own issues.
Forcing people back to the office
Why would you want to do that? Because you have the office and want an excuse for the expense? It won’t make for happy employees. You don’t care? Well, that tells employees all they need to know about you. They will resent you for it and will disengage or disconnect. They might stay but you might have destroyed any engagement they had left with the organization.
Many people I know will not ever again take a job that forces them back into the office every day. Not if they have a say in it and the circumstances allow for it. And even when you get that talent back into the office for some reason, they will leave as soon as they can. Any illusion of employee retention will be out of the window. Even when they stay, when they have no other choice, they will be less engaged. Force and threats are ill-advised management techniques. It won’t help you in the long run.
But people need supervision
Do you think they need supervision? Maybe if you are a kindergarten teacher. If that is not the case, did you hire the correct people? Do you really think they need that to be more productive?
Modern offices are often not about productivity but about cost optimization. Landscape offices and other nonsense have destroyed more productivity and killed more interpersonal collaboration that it ever created. they exist to reduce costs while catering to lazy and easy management. Make sure everyone is at their desk or in a meeting room. Attendance qualifies as output, maybe even as an outcome. Horrible! Presentism is dead. It was and has always been a retarded business practice.
Keep offices where and when they make sense. Be bold and brave when it comes to moving away from them in other cases. Position yourself for the best possible outcome for your workforce and your business. Also, don’t forget that offices tend to be in cities. Cities are costly places to live and real estate is small and expensive. Being there and working from home during a pandemic is not all that fun. Especially since all the benefits of a city are missing with pandemic measures in place. I know many have dreams of ideal cities that have wonderful living conditions for everyone but which should help us cope with energy consumption, loss of open space, and reduce global warming. But you cannot live in dreams. Cities also don’t address the real issue of too many people on too small a planet that has become a village.
But people are social animals
Yes, and they can have more time to socialize at lower stress levels when telecommuting. They can work and collaborate with colleagues within and outside of the company in a coffee shop or meetup space once in a while. The professional development is often limited by corporate office borders. There is so much to learn from collaborating with others.
They can attend conferences and community events, they can make it to user groups on time since they don’t commute as often, … there are so many other opportunities to socialize and be productive outside of the office. I would not be the professional I am today if I had stuck to the office as a place to socialize, work, and learn.
Really, we can keep going. But I see a lot more excuses than I do genuine reasons trying to dispel that the office is a relic of the past.
Use the pandemic as a learning opportunity
No, I am not just talking about self-study in some of the time freed up by not having to commute.
If you are only interested in maintaining the status quo in order to avoid losing power and budgets you are delaying the inevitable while costing your company dearly. You are throwing good money away whilst missing opportunities and losing talent. The latter both in recruitment as well as in turn over. Many companies will make that mistake. Governments as well. I can already notice the discussions about the financial impact on public travel and the need to get commuters on board again. Despite congestion, pollution, time lost … all to keep an old economic reality going.
Last but not least you are proving yourself a hypocrite. Harsh, but true. All the babbling about “the only constant is change” to your employee over the past decade goes out of the window the moment it disrupts your comfort zone and challenges you to reinvent your self.
Really reinvent yourself. You can no longer pretend change is moving from Skype to Teams, from VPN to VDI, or from PIN to contactless payments. Those are technical evolutions. Just like a new office building might be more energy-efficient or comfortable it is not a huge change over the older one. Changing how you do organize your workspace and workforce will require a real effort and change, also from you.
The fact that some managers need to physically have their employees in an office and meeting rooms is worrisome. It is very limiting and comes at a high cost. Sure actual problem is not the manager? It takes real skills to keep people moving in the right way effectively and efficiently. Office spaces are just one piece of a sideshow prohibiting real progress. It reminds me of measuring output instead of outcomes. Honestly, the office is just one more example of the many blunt instruments in our professional lives that stand little chance of making a real difference.
To conclude, is my statement that the office is a relic of the past correct? Well yes. Not for the full one-hundred percent of use cases but office space can be reduced significantly and the remainder can be leveraged in a modern, flexible way to your advantage.
Managers, get out of your comfort zone. Wake up and smell the coffee. Surely, you are not going to wait for the next pandemic to close the office for you, and for good at that time, are you? The office is a relic of the past, in many aspects. If you want to save it for what it is good for, you’ll need to get rid of the rest.
Disagree all you want but at least think and discuss this beyond the comfort of a status quo and routine. Think.