.
Good morning, R. I am G-FIN. I hope I am more developed the end. Yes. So, I am part of the
vegetable team, works in IBM. So, I sat in my career in like five years ago, I was trying
to integrate self with look for the algebra be side, then curl M mostly work in algebra
vector steps. So, this is a new project which we are working on. So, today I am plan to cover
following things. I will just give a brief and robot what is in the agent telling is what
it means, it means, different type of different things, but I will clear on that part. Then
what do we have in algebra at the moment, then I will brief you talk about cloud transition
with short because the demo is based on those things and I also mentioned before about
like S3 tape, what it is and FIN. So, what is intelligent trying? So, basically you need
to move the data across different storage mediums, maybe hard HDs, SSDs, that is the basic
idea. And here in S3, like we talk about storage glasses, purpose and storage basically.
So, faster storage glasses, you need to move the data from different storage glasses like
this standard storage glasses, then this glacier storage glass and all. And why we do not
do not do that? So, why do we need that? Because basically it optimizes your course
like you can keep the most recently access data in a faster medium and like the data
which is not that much useful, you can move Tesla or medium. And how it based on policies
like the policies maybe on the access time, like the oscillation access that I will
be in the first medium and not much like it will be on the slower medium or after time
say 10 days you need to move this data to another storage glass kind of.
Now, what do we have in algebra? So, if you know like there is a placement targets, that
is what we call like in which we can defend different types of storage glasses and each
storage glasses represent one pool. So, if a pool is created on a faster device,
then you can name it like fast something like that. And this is, by default it creates
pools on the safe cluster, but I am talking about like you can also specify pools in
your data can go on. And as I mentioned before we have storage glasses which is similar
to what it provides, but yeah it based on safe pools. Then how we do the data transition
or data movement like again with a safe cycle policies. So, we need to set that policy
on the on the buckets. And one thing is like, so the placement target, what do I say?
Like, so this need to be mentioned when you create a bucket. So, that is because there is
a default placement constraint like that we need to mention that. And you can mention
the storage glasses for the object operation like you can say if you put an object in a
different specific storage, then you can mention that.
So, that is a manual way of doing it. And after that you can automatic or like you can
do a life cycle policy and that I will more cause different storage glasses. And all
the configuration are defined in the so on so on view level. So, the placement target will
be defined in the so on view level. And the so on level we will define the storage glasses
because in as w, the so on of persons the pool basically like you most of the times like
if it is a defaulting then it will be a defaults on, but here you should.
Yeah. Now, as I mentioned earlier so I have mentioned about like the data movement across
different storage glasses. This is bit more advanced or not advanced, different use case.
So, here the movement is happening between RCW which is a on-prem and other one is like
the cloud endpoint. So, the cloud endpoint need to be like more like an ST combatable
thing. And so, here the so on level configuration is not required. In the placement view
you just define the storage glass and the storage off you need to mention the configuration.
So, this is a special type of storage glass which is not cloud a street. And you need to
provide the like the S3 and point details like access points, we can and if you
want to mention bucket which bucket you need to put the data under. So, basically this seems
to be bit controversial in the sense like the on-prem attribute data is more
across cloud cloud you know it is ghostly and on-prem is cheaper. So, this is kind of
first step we are trying to sing with cloud thing and yeah in the later slides the
indelgenting or like the tm which you are working which makes make sense if you
if I mention the ST tape. So, yeah as I mentioned this is a unidirectional process as of
you know and like I mean as of now in the sense on the later series the
skewed one like it is kind of a solid the like it is unidirectional the data will move to the cloud
but you cannot access the data after movement. And you can we can the head of it. So, you will
have an offense in the on-prem cluster and you can look on the data on the cloud. So, that is
cloud tension and so, this part is more is in the master's of so, basically this adds the
restore capability. So, we try to map the restore functionality with restore APNST but again in
a three the restore APNST is more like you need to move the data from a glacier to the standard
sorry task kind of thing. That is why the APNST is used but we are just trying to adopt the APNST for
this purpose this use case like if you you send list of the cost from the attribute cluster
then it will pick up the objects from the cloud. Again there is also you can use a normal
get-tropation and on which is kind of a way to like in which you will you won't know like it
will assume you see down on the data from the cloud and then you can access that if you
will send get-tocus or something like that on the head of the object. Now so, there are two types
of restoring so, one is temporary. Again it is based on the restore APNST which is three
powers. So, temporary the data will be stored temporary and life cycle rules which we are
written on the bucket it is not applicable for the data and there is an expression time like
in the next slide I will give more details about the STP. So, after that expression day
so, something like that that will be again move back to a step data like kind of a head object
so, permanent is more like the object will be stored permanently and so, there is no time limit
or something like that but the life cycle will apply on that because if you say 10 days after
the object need to be moved back to cloud it will move back to the cloud. Then one key difference
is that the restore type if it is a temporary thing then we are not doing it for the application
like multi set purposes we will just keep it a month soon because anyway the data will be
moved after something right or I mean got delayed after something but the permanent like the
data will be located on the different sources and for the get occurs this is for the VU sorry
for the STG get occurs if you say getting the object I asked to get occurs then the object will
be we store temporary purpose similar to temporary. Now this is how the APN looks like. So,
as I mentioned the STG the APN is defined to move the data from glacier or like low coastal
cluster high-speed storage class using list of objects but for our use case we are only supporting
one parameter in those circuits which is days. So, this is defined then it is a temporary straw
if day is not defined then it is more like permanent room. So, these are two options at the
amount which are available for this one is version ID. So, if you have multiple versions of objects
if you want to download one version of list of one version then you can do that. So,
the current version in the it will be moved like in the so if you have multiple versions say and
the four versions we moved to the cloud and the current version is five fifth version and if you are
doing a list of then it will list on the third version then the on-prem attribute will have the third
version of jet. So, the latest version will be all right that is what I am trying to say.
And for the this is for the list of object call like similar to that STG has a get call like
CPE or get of it called or will also will fetch subject from the cloud. For that you need to
configure two parameters in the TA config. So, one is which makes the like the get to cost
allowed a little like it will make the if the cost is initiated then only if this options
that then only the little will happen other on is similar to the list your days like how long
you need to keep the object on the attribute server. Now, this basically like the variation
thing like how we can see the object is transition back to the attribute server. So, we had different
headers. So, when you initiate the request it is a sync call from the attribute. So, if you
mark the object is like we saw in progress and when it is completed we will mark it is we cloud
will start if it is failed then we make it lists of failed again and all this can be found from
the rados admin objects chat come in as well as from the header like if you call as three
head of jet or something like that you can see that with your status that is come. Now, for the
permanent list we are currently putting back the object to standard storage glass like even if
we have multiple storage glass in the cluster we only put in the standard storage glass it is
can site like disillimitation maybe in future we will change it. But, for time the jet we are
not changing the storage glass it will be still pointed to the cloud test storage glass which you
are defined. Now, what is a street tape? So, most of you know type is like made chip storage which
is available. Now, most of the stream enders also supporting like the tape storage. So, basically
the tape like when I am as honest we all like versidity. So, basically the here the tape
have an S3 interface you can send call S3 causality. So, that is a basic idea and why people are
doing it. So, basically the tape like the it is causer fatigue and like it is more doable than
the other type of storage mediums. And yeah, so the thing is that integrity and market and support.
So, this is like the features of tape which can be. So, here basically tape is kind of a different
storage glass and you can we are moving a data from the S3 object storage tape. We are again
to S3 con. So, as I mentioned we only support S3 on the RGB level. So, this can be also consumed.
So, the plan is to integrate with different type of tapes and since we have working IBM first
goal is to integrate the diamond tape which is the type solution which IBM provides. So,
this is like ongoing work. So, we are trying to support a different type of storage glass
on a cloud as thick ratio and the PIS already the name we need to add the extra facility.
So, this might be more sense like from indignity in purpose like the yeah, moving a data
to a tape store is then and cloud or like more closely thing. So, we came also on like we need to
define policies which will automatically the things. So, that is the next step and
other thing is we need to add more debugging purpose in the for the use of positive because
here you are need to debug two different two different storage mediums one is on the
side and other is outside of the stuff. So, yeah this two do is also like a tackling which all
the things are pending from our side of which are ongoing things yeah. So, any questions I will
go through demo if you want to ask a system we can ask a system after demos which might be more
clear like how the things will work. So, this is a coded demo and I hope it is visible is it
visible in the back end. So, basically I have created a safe cluster and using this chart
so, my actually sounding and if you just check yeah it is as of now I am T. Now, I need to configure
the I have configured the I have configured the what you say the cloud transition things here.
So, basically I have like a single node cluster so, it is a default sound group and if you go
I have defined the placement and the is a cloud IBM storage class. Now, I have defined
the like T a configured I am it as like and poya and this is a cloud us see type and on so, yeah and I also
said some configuration like it is kind of two configuration so, which will simulate that attack
transition we store instead of days like one day will be come to one 20 seconds for for example and
here for the waste already like how long the waste or like how long the object will be it will
be 60 seconds it is kind of simulation purpose. Now, I am going to create a bucket
bucket is calculated now I need to set the life cycle rule. So, yeah if you have mentioned
one day after that the object need to be transition and I have given the cloud like the storage
class so, stored IBM. So, this is the an APA to put the life cycle configuration on the bucket
basically now I need to add some data so, I am just
also this is a cloud endpoint which I have afforded in the TA config. So, if we check on this
and point at the moment yeah there is no bucket name BCT which I have created earlier so, yeah
so, basically I am copying certain data to the bucket and see the transition happening then
I will call this for a question.
So, this is basically this subject call it will show the head condons you can see the
storage class is standard at the moment. So, I have created three files on its
permanent one for its two and four temporary so, all of them has currently standard storage class.
So, the transition not happened so, just take some time and just forwarding a bit.
So, one thing we do not know that m time won't be changed for the array process. So,
we can not do m time
Now, you can see all the that I got transition. And if you check the head of it again,
now, the storage just is cloud IBM. So, this is the permanent was shopping.
As you can see, the object got was stored here, but I am time is same.
So, in the demo, I face a mixture. So, basically when I try to reassure the objects, the
first object got transition back to cloud. So, that is why the permanent is fine. So, now, the
object got was stored. Finally, I am going to go into the way through.
So, as you can see, like, it is just small object like it got to be stored so fastly.
Otherwise, like it will just complete all the course, but it may take some time on the back end.
Now, I need to show the permanent again, because the life cycle will kick off and like it passes
from and of it back to the cloud. Now, I think I have all the sets. Now, if you check the head of
jets, I mean. So, you can see the permanent has the storage last standard and yeah,
other two has cloud IBM still the storage. The size is changed, but yeah, otherwise, storage
was still the same. Yeah, you can also just show in the back tab to the head.
So, that is the demo. Any questions?
So, the question was how the core time management for the storage classes, like how you
can manage the core terms, different storage classes and so on. Actually, for me, the last
condition, then only I came to know we have issue with the storage class,
cortices. So, like for me, the last condition, we have mentioned like we have the issues
with the cortons, storage classes and so on. So, then only I came to the issue with that.
So, we look into that. So, yeah.
I mean, also I found it is not possible.
Yeah, I found it is not possible.
Yeah, I found it is not possible. Because this feature both developed as a
other economist possible on this, this was featured like parallel with the
conning thing. We never test the conning thing against the issue.
The question was, the question was whether we get bucket notification on the
list of the class. Again, it is not implemented like it is two
delicas on our side.
That is good.
Also, regarding the namespaces of the beggin start. So, you have like your namespace on these
red or spooks to give a side and then you have your backup namespace.
And so, how is the name pollution for bucket names managed in that regard?
The customers, the namespace on the self-cluster and how we can manage the
namespaces in self-cluster and the tape cluster of the cloud back in.
So, actually, we are not creating a bucket on the cloud back in.
So, it was on the demo since I forwarding it to what to remove.
Basically, we are just creating path kind of stuff on the bucket.
Like, it is an object we are just showing it to a bucket which is mentioned on the cloud.
So, we are not creating a bucket. So, the type of pollution won't happen as far as I understand.
We got in the users, I think it is all in a string, because the sending from
AGW to the end user. So, AGW does not know about the user.
Like, it just has the credentials. That is it, nothing apart from the user.
So, AGW is not available to the users or something like that.
So, that again ties into the way to the invoice potential customers
on the back end storage usage.
So, yeah.
Yeah.
You don't want to sell it for free.
So, yeah.
Let me tell you some of how the testing that you can see how the test features
use as well.
I mean, it is triggered by the client.
It is also important.
Okay. So, the customer is kind of matrix from the client side here.
The matrix which how much the customer send from the client for the story and on.
Okay.
How many of these stores they did for example in the last 24 hours?
Yeah. So, the customer send matrix all like.
So, basically we may need to add the telemetry part, I guess, which is like the most
or because it is not added.
Similar to get to a put, we may need to add the rest of the telemetry side.
Okay.
Thank you.