A Singular Approach to DevOps Across Multiple Clouds

Bill Manning , Solution Architect

November 10, 2021

< 1

The multi-cloud market momentum is now well established as a strategy for avoiding vendor lock-in, choosing the best-fit cloud for each workload, proximity, and optimizing your capital expenditure. These benefits are even more compelling with a well-crafted approach that mitigates the impact of different technologies and unique processes across cloud vendors. In this webinar, we’ll cover: How the JFrog Platform masks the differences between cloud vendors Empowering you to embrace flexible vendor choice while adopting best practices for SDLC A consistent operating model

Speakers

Bill Manning

Bill is a Senior Solutions Engineer with JFrog. He is also a mentor with TechStars (Nike Incubator), Matter, and NestGSV. He has successfully exited 3 companies and took one public in Australia. He also currently helping various startups as an advisor. In his spare time, he likes to travel with his wife and two boys. He also plays guitar, lives for the beach and rides skateboards.

Video Transcript

good morning and good afternoon everyone
my name is courtney gold i will be your
moderator today i also have bill manning
here with me
you’re your speaker today just a few
housekeeping tips before we start we are
recording this webinar and this will be
sent to you post of it also please
please please answer or ask any
q a we will be here to answer those
whether it’s during or after the webinar
is done
um other than that i will let
hey everybody how you doing uh this is
bill manning um i’m you know going to
discuss today basically is called the
singular approach to devops across
multiple clouds um i’m bill manning i am
actually one of the solution architects
here and i do a lot with our customer
base i actually said i do a bunch of
webinars public speaking blah blah blah
all the usual kind of stuff um but the
main focus of today is is uh you know
basically a lot of companies these days
are choosing um things like multiple
clouds right you know and we’re going to
discuss some of that the benefits and
why you would do that we’re also going
to talk about how we you can use our
platform as an approach to actually
unify everything together so that
non-dependent on how you host it even in
the hybrid model um you know that
basically our platform can help you
through the entire process from end to
end and make it so that you have this
unified experience while still having
underpinnings of all the other kind of
providers that are out there
now of course i mentioned here of course
you know google cloud azure and aws you
know the the major three that everybody
knows about of course there’s other ones
like oracle cloud
other providers out there too that
provide iron and things like that i’m
not going to go too heavily into them
i’m just using them as a primer to say
you know we understand that there’s a
lot of offerings out there these just
happen to be the big three but there are
others out there also and this applies
to those others also
um
so understanding that you know the first
thing we want to discuss is of course uh
just as a uh
introduction just so people understand
uh when i say unified
and i talk about our platform it truly
is an end-to-end platform and i’m going
to touch on some of the components today
um just as a quick overview artifactory
the universal binary repository manager
it’s a place to manage all those
third-party transit dependencies you use
as it is a software development team uh
85 to 95 of your software is someone
else’s but it’s also an exceptional
build management tool and a software
also uh you know life cycle management
tool in addition so it’s a place to
store your builds it’s a place that you
can go ahead and actually emulate your
sdlc your software development life
cycle it’s a place for accountability
understanding how things were built uh
and adding as much information around
how things are built so they become more
relevant to you as an organization to
the right of that we have x-ray it’s our
security vulnerability and license
compliance tool it ensures that those
you know 85 to 95 percent of those
binaries that you’re bringing in and
consuming as an organization are safe
and secure and compliant it can be
integrated in everything from you know
you hear the term shift left all the
time so we have integrations into ides
we have a cli tool that you can utilize
at the desktop uh you can integrate into
your ci process and you can even do it
into your release process and your
distribution which is to the right of
that our distribution is a way for you
to go ahead and i’m going to talk about
actually distribution in depth as part
of this because in some cases you might
want to have other cloud providers just
be hosting providers or you want to go
ahead and actually have it so that your
software is spread across multiple
regions and multiple cloud providers and
to do that you can use our distribution
platform distribution is the hub and
then we have
lightweight immutable versions of
artifactory called edge nodes these edge
nodes can be placed in these other
regions and it’s a way for you to
actually you know maybe push things out
and deploy them and to say
say you’re deploying a web service and
you want to have a multi-region approach
you can go ahead package up the things
that you do with our distribution hub
into a thing called the release bundle
which i’ll talk about which is a
digitally signed immutable release that
might contain things like helm charts
and docker images for a web service and
then you can publish those out to the
edge notes for easily consumable objects
that makes it so you can destroy you
know distribute your actual web services
more succinctly even across multiple
cloud providers
below that we have pipelines this is our
cicd and ci orchestration tool uh you
can use it as a ci tool you can use it
as a ci extension so if you have already
ci processes in place and you want i
want to add additional functionality
such as blue-green testing or approval
processes um
you even have signed pipelines you have
a blockchain style ledger of everything
that you’re doing um you can also use it
just strictly for distribution and you
can also use it as a way if you have
more than one ci tool or one with more
than one ci environment to orchestrate
them together so you understand the
interdependencies between those builds
and at the very top of this we have
mission control and insight which will
actually become a key factor of this
when you are doing things like multiple
cloud providers because to us we don’t
care and i’m going to talk about that
too because we don’t care where you’re
hosting us we just care that you have
connectivity
one of the major things about the way we
approach things is that like i said
before it’s an end-to-end platform it’s
made to scale with infinity because the
thing is is we have customers that are
pumping petabytes of data daily through
our products you know it’s also
radically universal meaning that we have
over 30 package types you can integrate
with you can integrate into any
extensible system such as
ti environments other cd environments
it’s all api-able and it’s all if you
use our cli so it’s extensive you can
use us where it sees fit
all the time having things like
continuous security as i mentioned
before their x-ray product everything
from shift you know shift left at the
developer level where the roi is
greatest all the way down to ship right
where we are actually deploying the
things that you’re looking to do
and the main focus today is going to be
hybrid and multi-cloud right the idea is
is that we can provide a like basically
a base level foundation for you to do
everything on non-dependent on how
you’re hosting us and this is essential
to what we do and this could be one of
the core functionalities that we get and
we have a lot of discussions with this
around of some of our customers who are
looking to do this and we’ll talk about
some of the benefits you know of using
multi-cloud and also some of the caveats
and how we can use our products to
actually help you overcome those
and then lastly the ecosystem is huge we
actually have built our product to be
adopted by everyone uh so we actually
open our interfaces for enter you know
interactions there’s a lot of tools in
the market that have integrations into
us so we’re made to fit where we need to
fit but at the same time with that base
level functionality is very very
essential
so
one of the things we’ll talk about is
the optimized architecture of what we’re
doing today and the idea here is is that
as i stated we don’t care where you
install us right we can be in everything
from your self-hosted on-premise uh
where we
assess offerings you can use those in
combination together in the hybrid
approach which is the right of this you
know we’re even multi-cloud so even our
sas offering is multi-cloud we’re
available in aws azure and gcp but in
addition to that if you’re one of our
lucky government customers we’re also in
azure government and we’re also at aws
gov cloud you can actually go to their
respective marketplaces and utilize us
but really what it comes down to is is
that keep in mind that we are the base
for this we are the common connective
tissue that allows you to have the
ability to do hybrid models strictly
cloud multi-cloud and i’ll talk about
the various approaches today on how you
can utilize us to help expedite that
so what we found recently is that you
know cloud is much more than the
technology when companies choose to go
to cloud there’s usually a bunch of
different reasons and we’ll discuss some
of the reasons behind that but the thing
is is that whenever you look at people
and companies that say hey we’re looking
at moving to the cloud and you know the
cloud has become such a generalized term
these days basically when we say cloud
and most every company we talk to is
cloud hosting right we’re going to host
our applications but usually the
determination comes you know based in
various forms whether it’s a it’s a
mandate from up above a relationship
that the company might have with one of
the providers um it might be a certain
set of tools that are available for some
of these cloud providers somebody might
want to use aws code build other ones
might want to use azure devops right um
it depends really and it really comes
down to what the company is really
comfortable with in those natures but
there’s a lot of information that you
have to take into account and this can
be kind of staggering sometimes for a
lot of organizations
and the thing is is that as we talk
about this you know why would you want
to consider multiple clouds and this has
become a really common thing um in the
past you would just go with a single
cloud provider you would you know you
form a bonding relationship with them
and then the problem is with that
there’s some caveats that we’ll discuss
in a bit
but you know the thing that we see in
the industry sees right now is that most
companies 70 of the companies plan to
increase their their cloud budget going
forward this has just become the
standard right there’s a lower tco
that’s associated to it right the total
cost of ownership because you don’t have
to have the infrastructure you gotta
remember there’s like opex you gotta go
with you know uh you gotta think about
in budgets you know 61 percent of the
budget you know businesses have migrated
their workloads to the cloud just in
2020 alone i mean the pandemic had a lot
to do with it was decentralization right
in
its purest form and this allowed us to
you know a lot of companies to kind of
take a step back and say hey we’re doing
a lot more remote and we’re also you
know looking to reduce some of our cost
this is one way to do it so the thing is
is that in 2020 50 of organizations move
the majority of what they do to the
cloud for this one reason because of
things like tcl
now when we also think about cloud
adoption and stuff it says that you’re
90 of the companies are utilizing this
right and then 87 of those have actually
gone ahead and gone the hybrid route
some companies and we’ll talk about the
caveats because there’s still some
misconceptions or there’s some actually
good reasons why a hybrid model would
work best and i’ll actually talk about
that especially in terms of development
and software delivery and also just in
general utilizing both a hybrid model
and a multi-cloud model to actually
provide a super robust you know way for
you to go ahead and have things like you
know security reasons cost savings you
know backup strategies um you know the
whole idea of not putting your
virtualized eggs in one cloud basket um
you know the thing is is that there’s a
lot of reasons why companies are
starting to embrace this and the thing
is is that you know yes one of the main
you know motivations that we’ve seen out
there is modernization right it’s a huge
industry trend you’ll see a lot of cios
and csos and you know they’ll start
talking about you know what we need to
go ahead and budget for these things
because we want you know we read an
article somewhere sometimes it’s
strategic in nature also in a lot of
cases you know actually having that
infrastructure
um hosted by somebody else allows you to
focus on things more that are more
relevant to what you’re doing than
trying to maintain a physical
environment um the thing is is that
operationally you know data centers are
you know and regulations are one thing
you know infrastructure refresh these
are all the standard things you hear
what we hear actually from customers
right operational costs scaling out um
you know there’s capex versus opex you
know maybe when you start using cdns and
other network optimizations to make it
you know more robust and it’s funny is
the cdn and nikon network operator
optimization portion really started to
get more traction we hear more of this
especially you know if you combine these
with elements of things like footprints
and geographical expansion especially
with the covet over the past 20 plus
months
um you know the main thing there was is
uh teams you know working home and
working more remote and it made more
sense to start thinking about these
things because of the fact that you know
we became more of a divested
infrastructure than the typical office
model right
now saying that
oh come on switch there we go
there are benefits to actually having
multiple cloud providers um instead of
just one right it’s vendor flexibility
and when i say vendor flexibility i just
don’t mean um you know competing one
provider against another what i mean is
once again going back to the idea of
tool sets you know there are certain
tools that are only available in certain
cloud providers um it also improves
disaster recovery i mean you know we’ve
seen it less over time as these cloud
infrastructures have become more robust
but it is still there’s still a vex on
it that you know people still have this
anxiety of saying you know i host
everything in aws us east one that’s the
most used aws region um what if that
whole thing goes down or what if aws
suddenly has a dms problem um well you
know what if i have something in azure i
can quickly go ahead and you know maybe
move all my operations over to a
different cloud provider um and the
thing is is that it also helps also
discrete you know decrease some capital
expenditures when you are doing this
because you’re kind of diversifying it
and stuff like that and some cloud
providers will actually go ahead and
discuss terms and usage and things like
that but that’s i that’s not stuff i
deal with this is stuff that you know
you would deal with in terms of
um you know more of the managerial side
budgetary constraints and whatnot but
you know we all know the fact that
moving to the cloud in most cases is a
way for you to lower the costs but it
does come at a cost and that’s the thing
is is that there are challenges right so
you know understanding when you look at
a cloud provider assessing it and
identifying which applications and
systems need to go there right
understanding different cost models is
it infrastructure is a service a
platform as a service is it sas right
there’s a lot of things like that also
too when you start looking at deployment
models you know your public versus
private um you know as a hybrid cloud
model as a multi-cloud model um you know
choosing the right providers vendors and
consultants you know you are gonna have
to take out a whole bunch of new you
know skill sets when you’re dealing with
this also when you’re doing the
migration how do you maintain business
continuity this is a huge one we see
this all the time we i’ve had customers
that you know peel the band-aid off and
do it over a weekend i have other ones
that are like we have an 18-month plan
in which we’re going to be migrating all
the things that we do because we just
don’t have the capability to bring down
any of our services during that time
it’ll affect revenue
the other thing too is is when you start
looking at this
is coming out with all the proper routes
for you to go ahead and actually you
know create these kind of models and
understanding what the cloud routes that
you can do are right is it re-hosting
are you reshaping are you repurchasing
are you re-architecting there’s a lot of
things you need to take into account
when you start thinking about this and
for a lot of corporations this is a huge
herculean task
and the big thing is is that you know
when you do have the challenges you know
training and certification become a
thing um you know what i mean just
because i know how to use aws doesn’t
mean i know how to use azure or gcp or
you know one of the other multiple cloud
providers you know you need to bring in
talents like cloud architects network
engine cloud network engineering
automation engineering security
engineering and you know cloud
developers um you know there’s also
questions about adequate security you
know how secure is my stuff that i have
there like you know you have things like
for aws you have aws direct connect you
know this basically like a vpn directly
to your instance and you can actually
have more homogenized control around
this but others might not have that you
know provider and the thing is too is is
that there is always you know planning
minimal description and also additional
costs
you know we talk cost always comes up is
always the major factor in but you know
in budget and there is a a portion where
you need to go in and invest heavily up
front to gain the actual you know uh the
benefits down the road but these are
just things you need to keep in mind and
you know one of these were to discuss
here is
how can the jfrog platform
really help you get through this right
and that’s one of the key factors
because of the fact that we handle
things like your production side right
we handle the development side it could
be your qa all these things that you
rely on to get your software to where it
needs to be
and during this time period you want to
have a foundation that you can build
upon that will allow you to do these
things where you can start off with
maybe on premise or you’ve already
started on premise and how do you start
slowly migrating your operational
characteristics because i see in some
cases and i’ll just a little aside on
this i see a lot of customers are like
what we’re going to do is we want to
keep all our developers um you know
running locally in our offices in
regions and so we want to have a local
instance of your artifactory platform
that we you know jfrog platform that we
use already but we want to start pushing
all of our ci tooling all of our testing
tooling all of our distribution
components into the cloud because it
allows us to have a broader reach you
know this is a very typical scenario
that we hear or we’re actually you know
what we’re actually closing down our
data centers we’re getting rid of all
the costs that we have uh we are going
to migrate everything into the cloud we
do want to have multiple clouds because
we had multiple data center providers
before and we feel very safe and
satisfied knowing that
we have more than one organization
watching what we do because this is how
we make money and the money we make
allows us to pay you
so saying that you know when we talk
about a hybrid architecture you know we
see this approach with a lot of
companies like i said you know we’ve
been doing things in our dc’s for
forever um you know what though every
time we have to do a refresh of
everything that we do in our dc uh the
operational cost is terrible um it takes
down things it’s unpredictable so we
actually want to go ahead and we want to
start migrating some of the essential
parts of our organization up and if you
notice here you know if you’re using our
whole jfrog platform we have things like
you know artifactory our x-ray product
distribution and pipelines you can have
that same exact architecture in terms of
products in the cloud without having to
have all the heavy operational load uh
that you might have in terms of actually
having all your own equipment right so
all these things are there and then when
you get to these providers you know
choosing how you want to deploy them
this is always a big discussion you know
uh we’re exploring kubernetes we want to
start virtualizing and orchestrating all
the things that we do well if you’re
using our products once again we don’t
care how you deploy them as long as
they’re deployed properly you can deploy
us into an orchestrated environment like
kubernetes or openshift you can deploy
this as you know um docker images and
have them running in the various even
just individual docker services you can
install us as actual you know virtual
machines like ec2s and things like that
you can utilize the external service
using our high availability say you’re
using aws you can use services for
storage like s3 and use rds for the
database if you’re in azure you can use
the azure blob storage right so there’s
a very flexible approach too when you
start going from your hard-pressed you
know self-hosted dc environment which
you can still retain but then you start
emulating all those other factors and
utilize those services
that those cloud providers provide to
make your infrastructure in the cloud
more robust
so when you start thinking about that
you know the typical thing we see is is
that we have a data center maybe
we’re doing things listing cloud
provider we don’t like i said we don’t
want to put our our eggs in the
virtualized basket but in this case you
know you’re given a mandate as say an
individual you’re part of the
infrastructure team um your cio comes
down and says hey guys by the way we’re
going multi-cloud approach i know we
have everything all the development
stuff that we do right now hosting in
our data centers we want to move them
out to one of the cloud providers can
you provide me with a strategy that will
make things easy well if you’re already
at artifactory customer the nice thing
about it is is that you can have your
artifactory currently in your
self-hosted solution install us into
your multi-cloud environments and then
suddenly you have options on how you can
actually go ahead and utilize our
platform to ease this approach and give
you that base level foundation once
you’ve actually gone ahead and you know
you do it and then you can start
bringing in all the other ancillary
technology stacks that you might bring
in such as like your ci servers uh you
know your distribution servers testing
tools whatever but you can utilize us as
that common thread between all these
providers that allows you to share the
things you do those third-party transit
dependencies the build you produce the
production level instance components
that you want to point your environment
and you can utilize this as a way to
make sure that they’re all in sync
non-dependent on where it’s where it is
because we don’t care you know it could
be an azure it could be aws it can be in
you know google cloud it could be in
your data center and you know the schnoz
berries tastes like schnaazberries
they’re all they’re all the same thing
across the board there’s no variance
between them because to our platform it
all looks the same underneath and the
underpinnings don’t really care
so before you begin start and you start
looking at you know maybe moving if
you’re already an existing customer um
these are some things i want you to keep
in mind um always plan your your
migration and your replication strategy
because we’ll talk about that today
always clean up your instance right you
don’t want to replicate garbage we have
plenty of information on there on how
you can go ahead if you design your
repositories properly uh you know being
able to go in and actually uh clean
those up so you’re not moving garbage
but also to you know start backing up
and have backup strategies but at least
first sit down and when you plan this
you know look at all the pieces you have
currently
and then organize them so that you
figure out how you want to migrate the
various aspects of your organization
going forward
so the thing is is that you know what we
offer as a platform we offer a whole
bunch of different tools to help
normalize the experience of actually
going ahead and moving from your
self-hosted or a cloud or expanding as a
multi-cloud or whatever this is
applicable non-dependent on strategy and
not dependent on the actual
infrastructure in place
this is where we help the most we help
lower that barrier to entry by providing
the same experience no matter where you
have us i’m going to accentuate that a
lot so if you get sick of hearing it i’m
sorry but that’s one of the major things
that we do
the first thing you want to know is is
that how do i get all my users groups
and permissions synchronized across
multiple instantiations in different
locations right i i want to make sure
that my permission models do not vary
between myself hosted or between cloud
providers if bob goes in and logs into
an instance and you may be using a load
balancer that might be geographically
based he should have the same experience
no matter where he goes and he shouldn’t
even care what provider he’s on and so
for those permission models we have
access federation this is part of our
enterprise plus offering um as part of
the platform what this does is is the
more instances you have and if you
notice here by the way i didn’t put down
cloud providers because i don’t care
and the thing is is that once i have
these set up we have a circle of trust
that we enable between these instances
of the platform but allows me to
synchronize users groups permissions and
access tokens across multiple instances
so bob isn’t suddenly contacting it
wondering why he can’t connect when you
know and just he doesn’t know that he’s
connecting to gcp he doesn’t know he’s
connecting to azure he shouldn’t you
know he doesn’t know he’s connecting to
um you know maybe aws or
oracle cloud or one of those he
shouldn’t care he should be able to go
in be direct redirected log in and get
all the things he needs and get his work
done
so we have star based replication and uh
federation and we have mesh based so if
you want if you want to have one
centralized instance maybe your san
francisco self-hosted um is the is the
center point for your devops universe
and then maybe new york is in aws paris
has gcp and in bangalore you know
they’re running azure
it doesn’t matter if the thing is is
that you can actually have it so that
san francisco would then dictate to the
others if you want them on equal footing
you can set up a mesh based topology and
by the way this extends down to the edge
nodes which we’ll discuss in a little
bit too i can control the axis level
controls at the edge itself
so this is one way of handling things
like permissions and users
the next thing i want to talk about
is the fact that when we talk about this
it also it handles entitlements you’re
also leveraging the access
synchronization and this will build that
global model for you and you could also
use it for your ci tooling right so this
way you can also share those access
tokens you might use for your ci tooling
itself the next thing we want to talk
about is replication right replication
is one of the core components of what we
do um with our our platform right let’s
start with artifactory
five six
i lose track of time seven years ago um
when we started doing this a replication
is a way for you to make sure that
consistency is a paramount feature right
that when you’re an organization and
you’re using our replication strategy
once again i don’t care where i go when
i’m connecting if i’m using say a geo
load balancer in this day and age of
having distributed workers the major
thing is that my stuff is there the
things i have
so the thing is this allows you to even
do this across even multiple teams right
so you might have a team in india you
might have one eastern europe you might
want to have in east coast in us one in
south america um doesn’t make a
difference it provides consistency
across the team so my team in bangalore
when they’re downloading and
constructing uh a build should be using
the same third-party transit
dependencies that are being utilized say
in in my san francisco office or in my
buenos aires office
it also reduces latency a risk of making
sure that you don’t have that
inconsistency excel
you could also go ahead and also set it
up so that it’s it’s done not just at a
whole level so it’s not an instance to
instance it’s actually more of an a la
carte method you can choose what you
want to share between locations or
between cloud providers if you wanted to
it doesn’t it could be push or pull
we’ll discuss that it has many different
use cases it can be applied to them it
doesn’t matter on network topology we
don’t care once again you know where you
host it doesn’t make a difference you
just got to make sure you have the right
rules in place oh that was weird it went
back
back hold on it’s going forward now well
let’s talk about you know optimization
the thing is is that
our platform has had this built in for a
while so it includes things like you
know uh basically optimization behind
the scenes on the network and we’ll talk
about that you know especially when in
terms of uh we use if you’re not
familiar with the way artifact restores
its artifacts we store the artifacts in
a checksum based approach and i’ll
explain in a bit how we actually use
checksum based replication so that when
you are transferring objects between
locations one of the nice factors of it
is is that you’re not transferring all
the artifacts you’re transferring the
deltas between versions um so this is
just so you know one of the major things
behind this but we also use that same
level of checksum based replication when
we publish out things to the edge nodes
when i mentioned the distribution side
before i’m going to talk about that in a
bit but that’s all checksum based
meaning you say you have five terabytes
of a build right or high terabytes
that’s a big build or five gigabytes of
a build and the next build is only a
slight variant a 10 deviation between
the previous version when you’re
replicating these out we’re only
replicating out that 10 percent or if
you have a release bundle pushing that
10
so it actually makes it highly effective
and efficient
so we have different types of
replication right
oh this thing made a little weird
uh we have push-based replication um so
push-based replication means they have
location a pushes an artifact to
location b right we also have pole base
replication where maybe location b might
be pulling a binary from location a so
this actually helps um
well yeah yeah sorry about the
formatting here
i guess i got upload it gets uploaded
weird but um pull-based replication
means that this can be utilized by the
way in terms of of having it so you
could have either schedule or event base
right so it’ll be real time based on the
new binary gets uploaded or it could be
cron based maybe you do it every 12
hours you replicate between things but
what happens is is in the push based
replication the source it gets an event
that says i need to replicate this out
and it pushes it automatically to the
destinations it could be more than one
association two by the way so you know
then you have the other side where it’s
event based poll or a cron-based poll
where the source says send an event to
the target and the target says i’m gonna
download now pull-based replication is
great for places that might have uh
latency or low bandwidth these are ways
to alleviate that so this way remember
downloading is usually faster than
uploading so this is one way to
attribute to it
you can also go ahead and do things with
multi-site replication too where we
actually even have star and mesh based
topologies you might have one where is a
central source of truth maybe in this
case on the left hand side location a
and this one would actually go ahead and
you can either do pull or push based
mesh star replication out or on the
right hand side where you have two
locations and this gives you the ability
to actually have mesh based topology
replication between them so that you
might have two groups that are constant
synchronization with each other so these
are all open-ended options on how you
can do things
one of the other things that we just
introduced and this is actually one of
my new features my new favorite features
is the fact that we also have federated
repositories now federated repositories
are amazing and actually instead of just
discussing that i’m actually actually
going to go ahead and show you
the um
so let me go ahead and i’m going to
connect to my instance here
and let me bring it up oh why am i not
sharing here let me share
i’m going to share a chrome tab here i’m
going to share a window
so here we go here is um here’s
artifactory right this is my artifactory
and as you can see by the way i have
instances globally around the world
right i’ve got four instances i can have
them on various cloud providers i don’t
care this is our mission control product
that lets you know the current state of
what you’re doing
but one of the coolest new things that
we have is if you look at our
repositories that we have say local and
remote repositories local is where you
store your binaries and remote is where
you actually you know use the third part
of the trends of the source you proxy it
through
any of these repositories uh that you
have here if i just select any of them
at all you can convert them over to a
thing called a federator repository
now what a federated repository is
simply is this i can go in and select a
repository that i have here i can go
select and say hey by the way i have two
other instances i want to share this
with i select the repository i can go in
and say hey i want to share with my new
york instance and i want to share with
my bangalore instance now in the past i
would have to go to each location create
the repositories in each set up the
ability for me to go ahead and set up
the replication between them it’s kind
of an arduous process now if you have
two locations that’s easy three
it’s fairly straightforward anything
above that can be really kind of
daunting so now when you have multiple
locations i can select a repository say
i want to create this repository in my
new york instance and i want to create
this repository in my bangalore instance
i hit done
now what it’s going to do is i’m going
to hit save and when i hit save it’s
going to go to those two other ins
it’s going to create those repositories
and it’s immediately going to start
replicating out the binaries from this
instance out to the others i just set up
full mesh replication non-dependent on
location only dependent on location of
the actual artifactory instance and
non-dependent on provider those could be
hosted in in self-hosted dc’s it could
be in azure well i’m in you know aws and
gcp don’t care we’ve taken in that
straight out for you giving you the
ability to quickly go ahead and
distribute those binaries on where they
need to be
i’m super excited about this feature and
it makes me really happy but it’s meant
to be also it’s bi-directional mirroring
and it’s also event-based poll so it
actually pulls the binaries down so it’s
very expedient on top of that it
actually uses the checks based approach
so it’s only bringing down the changes
that it needs to bring down
the next thing i want to talk about for
just because of time purposes as we also
have jfrog distribution now jfrog
distribution the beauty of this is is
that maybe you have other cloud
providers out there right so maybe you
have it so you do all your build
services inside of say aws right and
then you you go ahead and you’re like
you know what we’re hosting in aws
um but we’re also hosting an azure and
gcp we want to make sure that we have
the best footprint uh globally that we
could have
now you could go in and set up
artifactory instances in each one of
those locations
right and that’s fine and maybe you have
multiple regions right so maybe you go
ahead and you have other instances of
artifactory you go ahead you have the
platform deployed in each one of these
use federated repositories to get the
builds on where they need to be
and then maybe in those instances you
have like your centralized u.s west
instance and then in gcp and aws
whatever but then you have other regions
where you want to deploy this
application now you go ahead and install
other artifactory instances and use
replication again
or you can use our distribution method
and set up these edge nodes so the edge
nodes are lightweight immutable versions
of artifactory and you can create these
things called release bundles which i’ll
talk about in a minute but this will
give the ability for you to go ahead and
actually build models that you can go
ahead and there you know these edge
knows that when you’re doing them
they’re read only they’re secure
right you can also use a thing called a
smart repository which is like a remote
repository except that the the actual
source is an artifactory instance and
you can actually browse it from the edge
note and and then pull and it’s
request-based cache
you can also use it for optimization
right so that we actually use an
optimization component to make sure
these are distributed more rapidly and
more efficiently
it also allows you if you are doing
things we have a lot of companies that
are trying to get their say their
software is to say like ali cloud inside
of china um
you’re going to be able to go ahead and
deploy edge nodes in ollie cloud and
then be able to have it so you can push
your binaries into there to actually go
ahead and just have it as a distribution
without exposing all the things that
you’re doing
but really what it comes down to these
edge nodes they’re they’re cheaper
they’re more efficient you can actually
just use them for deployment purposes so
you are deploying your web service or
whatever you’re doing in multiple
locations in multiple regions and
multiple cloud providers you can create
this gigantic star-based or mesh based
infrastructure
in addition to that i mentioned release
bundles now release bundles are great
you can actually go ahead and package up
things such as like i said a helm chart
and docker contains you know docker
images
place them together into a digitally
signed release right there actually have
their own bill of materials behind it
when we actually distribute them out
they’re actually validated to make sure
they weren’t tampered with you’re
actually gonna have our back control at
the edges so you could say who or what
has access to this you can use our x-ray
product to scan them one last time uh
before they actually go into where they
need to go and you can use our either
our api cli or you know jfrog pipelines
product you can integrate it to your own
ci process or your own cd process to
distribute these out and create these
release bundles it’s highly flexible in
its approach but we have a solid cd
model with the platform and the thing is
with our platform it’s end to end as i
mentioned before but the great thing is
is this is a level of consistency you
know from developer to deployment you
use the entire base of us and you have
complete accountability
in what was used how was it used um you
know where is it located in the future
we’ll have some more exciting things
even around security at the edges
themselves that we’ll talk we’ll be able
to we’ll be announcing um probably in
2012 we will be announcing in 2022 and
it’s super exciting i actually it’s on
the tip of my tongue and i wish i could
say more but i can’t
the next thing about this though is that
when you are doing this you know when
you have this distribution model like i
said
we don’t care you can have your
on-premise data center and publish these
artifacts out right these are your end
products your production level artifacts
these are the things you need to
download these are things you actually
might even use in another location where
you have geographically dispersed
individuals and this can give you a way
for you to actually go ahead and just
have you know they just need to pull
things and you get to set up an instance
somewhere in a region that some guy that
might be i don’t know in kalamazoo wants
to you know download something and this
just gives him the ability to pull it
down locally well you know maybe it’s
just all the third-party transit he uses
a smart repository to bring down all the
things that he needs as a developer
because maybe you’re constructing
everything you’re doing inside of aws
or gcp or azure or your own data center
it doesn’t matter but the edge nodes
give you the ability to distribute out
your production level artifacts into
various cloud providers in multiple
regions and multiple availability zones
if you need to
so saying that um i have you know i’m
going to go ahead now and just kind of
show a couple of the pieces here because
we only have a few minutes left behind
this and then if there’s any qa i’d like
to actually uh take some questions but
let me go ahead and let me actually
share with you just some of these
components and actually how easy it is
to use
so if you look here at what i’m doing
you can see as i stated before you know
our entire platform is actually designed
to be a global non-dependent on
infrastructure entity
so what you see here is actually
what
am i screaming no shaders oh i am sure
okay
uh it should be scared okay it took a
minute to share sorry i was sharing it i
thought i was anyway um just so you’re
aware you know having all these various
cloud providers that you know or
infrastructure doesn’t make a difference
you know here’s my main location um
here’s my new york instance here’s my
amsterdam assistance and it actually
said there’s a problem with it i know
there’s an issue with this and i can go
investigate
i actually see this might be you know i
think you know this is in bangkok you
can see i have edge nodes evenly
distributed in here and i can actually
if i wanted to by the way i can click on
any of these edge nodes like this and
i’ll just show you is that when i go
into an edge node
i can actually have it so that it
connects to this provider i’m going to
log in
in this case it’s going to have me
actually enter my password hold on
there we go
and when i look at this edge node you
can see that i have a whole bunch of
packages available
and if you look here you can actually
see that the artifacts are what they are
right so i can even show you i have
things like smart repositories where i
can go ahead and this instance is
actually connected to a remote instance
in this case this is actually connected
to a sas instance i have so i’m actually
even able to go in
and even do it where i have a sas
instance and i also have a self-hosted
instance and a hybrid model in this case
and i’m actually even able to proxy the
binaries from my sas instance down to my
localize instance and you can see where
i have i have actually the ability to i
can go in and actually look at the files
and i feel like it’s not being cached
but i can download these at any point
and you can see under here that i
actually do have some i think i have a
couple in here that actually have some
binaries that i’ve actually pulled down
in terms of smart live cache i might
have actually take got rid of them but
the idea is is that this is just like
artifactory right i can go in and use
all the set me up instructions and grab
the code snippets i need to connect to
it but these are read only this is all i
need to do is consume binaries
you can also see you know artifactory
here’s all the builds all the packages
all the binaries i do here’s our
distribution hub and in the distribution
hub you can actually see where i’m
actually going in and i actually might
have a release here right so 1.0 of this
release you can see where i’ve actually
distributed this out and there’s
actually a failure at some point when i
was distributing and i had an error huh
that’s interesting or you know the fact
is is that here’s all the contents i
pulled this out of the build i actually
went home you know i went ahead and i
asked some release notes here that i
might you know that represent what i’m
doing if i had the x-ray component
enabled in this case i would actually
just show you that there’s x-ray
information i can also show you in this
case where the actuals you know where
the actual you know if it’s been
produced by one of our pipelines
but you can see that when i look at
these if i were to go ahead and build up
these releases i could actually do this
automated style and say i wanted to go
ahead and distribute this out again
i could actually choose and i could say
is the is the target available in remote
you know in this remote instance i can
go ahead and select the edge nodes that
i want to do so i’m going to say edge
level one and i just simply do that and
now i’m actually going to go ahead and
distribute the artifact down to the edge
node where it needs to be and since it’s
checksum based if you notice here it
didn’t even bother to you know it just
went you know in this case it said i
already checked the a the remote
instance uh it already has the binary
i’m just going to mark it completed if
there is a new variant in there it will
actually only push down when it needs to
push down so this is more of the
distribution side
but the big thing is
is that i have these artifacts and i can
go ahead and show you that any of the
binaries i have and if i have more than
one location like i’ll go connected
let’s see i’ll just go connect to this
instance here um here’s my bangkok
instance you know where i’m doing
something and i’ll show you that we can
do is is we can look at you know some of
the binaries i have and i can set up
this you know binary replication where i
have say
i’m doing you know things like uh
you know i showed before one of the
repositories you know i set up the
federated model and i even go ahead and
say all right you know what i’m going to
create a a federated uh you know
repository let’s just do it right now i
might as well
let’s go ahead i’m going to create a
generic one
i’m going to say i’m going to go ahead
and create a federator repository i’m
going to call it i’m going to do a
generic one because i want to upload a
file of some sort um i love doing live
demos so i’m just going to say test fed
uh generic
and i’m going to say local it’s a local
repository here
um i don’t care about type i’m not going
to go ahead and add any security in
right now i’m just going to go ahead and
create the federator repository and
that’s it
so let’s go ahead and say test and i’m
going to say generic
right so i i created my uh my testbed
generic right here
um let’s go and copy i’m going to copy
the actual key because i want to be able
to just remember make sure i’m typing it
correctly
and let’s go in
and i brought up the other instance
right so let’s do this i’ll go log in
into the other instance i have so let’s
go take a look
at this one now this is my bank oh hold
on
when i don’t have the right password
all right so i’m going to log in so this
is actually um let’s go look at the
artifact registry here um as you can see
there is no there’s a couple generic
repos and things like that but let’s go
in and i’m going to say i want to go
ahead and i’m going to go create this
actually this this federated repo right
here test bed generic local and i’m
going to go ahead and say i want to
actually federate it out i’m going to
hit save
this is actually go ahead and let me
know that it’s actually created that
repository
let’s go ahead and look inside of
artifactory
let’s hit this let’s say okay here’s my
generic local repo there’s nothing in it
right now if i go to expand it up i’ve
got nothing
but let’s go over to the other side and
let’s take a look here and see if it’s
in here oh look there it is there’s that
same repository i created
now let’s go in and do something let’s
go deploy um i don’t know some sort of
file i’m gonna go select a file from my
local desktop um
let me uh i’ll just do an image why not
um let’s do a screenshot there we go i’m
gonna upload a screenshot i’m gonna
deploy this you can see here it’s been
deployed um into my primary artifactory
instance
and let’s go ahead and i’m gonna do a
quick refresh on this side and if i
expand it out
what do you know i instantly just shared
between two i created a repository in my
primary i created the
federated repository in another location
i uploaded the file and there it is
directly
that was it i just went ahead and i
could actually now span two instances of
artifactory in two different cloud
providers or a hybrid model and i’m
instantly sharing the binaries between
them that’s how easy it is even in that
approach and there’s multitude of
different things that you can do going
forward to actually enhance the
experience
but this is kind of the main things i
wanted to discuss today
um i just wanted to say uh you know
thank you for your time if there’s any
questions this would be now the time to
actually go ahead and do it i can’t see
the questions
oh there it is um we did have some
questions come in so i will go ahead and
just say him out live and then you can
go ahead and respond bill sounds great
um our first question is what do you see
as best practices in terms of trade-offs
on leveraging multi-cloud providers
minimizing complexity and overhead cost
in addition to that kind of question is
where is the right balance in your view
or your personal opinion
so
yes i i am one of these people uh that
when it comes to multiple cloud
providers uh i’m all for it and and i’ll
let me explain my background a little
bit uh before i joined jfrog over five
years ago i was the founder of multiple
companies and the thing is is that you
know
not you know cto and founder and always
understanding infrastructure cost was
always that you know behind the scenes
always in my mind right we always had
meetings about how much cost we were
doing so in terms of multiple cloud
providers there’s a lot of benefits in
each case right some have better storage
you know quotes others have better
transfer some have better tools than
others some charge for some services
over others
um but
reliability again consistency and and
the ability to have global coverage you
know there’s some cloud providers don’t
have regions that are handled by others
right so having that and and the thing
is is that
i wish at the time the things that i’m
showing here in artifactory when i was
doing it back then over you know five
and a half years ago um i wish i had
these tools now um providing that level
of consistency and lowering my cost of
getting stuff between locations uh just
from the actual aspect of trying to
figure out how to do it finding the
right tool doing all the deep level
analysis where if i had a base
foundation like our platform to do it it
would make my life easier it’s just
there and now in terms of using multiple
cloud providers there’s a lot of
benefits right i’m not the guy to talk
about it in those terms i think about it
in terms of of of deployment uh you know
in my old life like i said cost was
always the thing but in my terms is is
say i’m a release manager or i’m a
product manager
all i care about is getting my stuff to
where it needs to be as fast as possible
as rapidly as possible in the same
consistent manner
that to me is true tco right
the other stuff leading up to it the
cost that’s gonna cost you of course is
the education and things like that um
you know learning the platforms
understanding it you know deploying to
the platforms we see this all the time
you know there’s variance between the
platforms you know there’s basic things
you can apply from one cloud provider to
another but actually doing it is a whole
other story
so for me personally i’m a big fan i
like diversification i like
decentralization of objects right being
able to have it no matter where it is
wherever i need it i don’t care um i
just care about is is my customer
getting the best value
is is my support you know is my is am i
releasing as expediently as possible and
also is it as consistent as i want it to
be
because then if it’s not that’s when tco
goes through the roof
great um looks like we have another one
one more question this might be our last
one so if we have any additional
questions beyond this webinar please
don’t hesitate to reach out to webinars
at jcroff.com and we will go ahead and
answer those post events so not to worry
if your question gets missed or if you
think of something post-event um
alrighty so the next question is are you
intelligently defined different policies
for different geographies to cater to a
diverse regulatory landscape for
multi-site multi-geography development
teams
now that was an example of questions
yes
is that
you know
even when you can choose like say with
the access federation model right so you
can have it so that you can have common
users groups and permissions done you
can also have mix and match the thing is
is that
you’re not just relegated to say one idp
right one you know identity provider you
can have multiple providers and then
have basic rules based on that but one
of the cool things and i really i’ll
just show it actually is this and this
is actually one of the the new features
that we’ve actually introduced um it’s
my new favorite feature i am not going
to lie uh just let me know when it’s
sharing
i should be sharing by now i hope
come on
okay
and it’s called projects projects is a
new feature that we introduced a couple
of releases ago one of our biggest
complaints that we had was that before
you had super user and then granular
users and generated permissions now
those are fine and they were super
strong the problem is is administering
them was kind of hard we put a lot of
emphasis on administration and the
rights behind administration
projects
now you can go in and not only can you
have super user but now you can have
project level admins now project level
admins allow a little bit more group
autonomy now inside of there you can do
things like set storage quota and when
you define you know you have a hard
ceiling and a soft ceiling you can also
when you’re building these as a super
admin or you know this admin level
control building a project you could say
what they can do you know can they
control their own repositories um can
they manage their own members can they
manage their own x-ray resources can
they manage their own pipelines things
like that but if you look here we have
the main thing on what you’ve asked is
is that we have global roles that are
across all projects and artifactory in
general but you also have the ability to
create roles that are specific to those
projects now that’s great because then
you could say
what’s custom to that actual product
what’s relevant to that project and the
level of access control and you can do
this and have these projects in
different locations globally where each
team might have you know say different
roles and responsibilities
but using replication you can replicate
the binaries into those projects in
those regions and then have them
interact with it and i’m going to show
you a cool feature with projects
and this is in my opinion
awesome
one of the things too is is you you know
cross team dependencies is a very real
thing right across you know one team
produces something for another when
you’re doing this and you’re using our
project model what’s awesome is you can
do share and you can say i want to share
this repository as read only with these
two and maybe like maybe these two other
projects i have here and then they only
have read only access controls to it
it’s awesome and then or you can say i
want to share this with every project
maybe you have a common set of binaries
that are utilized for authentication for
all your products and one team produces
it they can include it in their virtual
repositories because if i shared this
out to another team and i’ll just show
you is that if i select another team
that i know is a shared repository you
can see where it’s locked here right so
this is a read only repository um so i
can go look at it but i can’t really do
anything with it other than interact
with the components in there but if i
had like a virtual repository and i
created a virtual repository like this
one like an iv one you can see where i
can actually have that actual live you
know that actual repository as an
inclusion and it’s read only so i’m
always assured maybe of getting the
latest version from the other team
without me having to hunt them down i’m
automating and i’m actually expediting
the process with a couple of button
clicks
and that’s the thing is i want to make
sure you know this isn’t just a product
for you know you got to think in terms
of not just getting binaries controlling
binaries but also to
how you utilize that infrastructure to
make your organization more relevant
efficient and keep the velocity growing
as opposed to pulling back and having to
come up with strategies that are old and
antiquated do it all behind the stream
i’m always i always joke around i’m
always like automate automate automate
this helps them right the more you
automate the more you can control on
other things
for some reason
um
something or something from the host
event you can email us at webinars
and myself and bill or somebody will
help answer those questions for you
other than that thank you bill for
joining us today and everybody else
thank you very much all right see you
guys
you