On 03/20/2018 09:47 AM, Brian Bouterse wrote:
I think the change would be positive in several ways. Snapshot is a
more familiar term that we can give content on what that means in Pulp
(content not settings). I think this will make Pulp more approachable.
It also aligns with the language aptl
Thanks for bringing up this topic. I feel like it’s been worthwhile to
explore it as RepositoryVersion isn’t a perfect name for the concept.
David
On Wed, Mar 28, 2018 at 9:57 AM, Dennis Kliban wrote:
> Thank you everyone for your feedback. I agree that snapshot carries some
> connotations tha
Thank you everyone for your feedback. I agree that snapshot carries some
connotations that are not congruent with the mental model we want to
present to our users. -1 from me also :)
On Wed, Mar 28, 2018 at 9:35 AM, David Davis wrote:
> I concur with @dalley. I read through the wikipedia article
I concur with @dalley. I read through the wikipedia article on snapshots in
computer storage again and it just doesn’t seem to fit our model. Snapshots
typically mean backups or archives and using them to describe the current
state of the repository doesn’t make sense. As Ina says, a user should
in
-0 to changing the name. Shorter is good, but I do think the name is
misleading, and I disagree with the reasoning provided in the meeting the
other day that "snapshot is more self-explanatory" - which I don't believe
that it is.
this term is not unique to Pulp so it is easier to explain to the u
On Wed, Mar 21, 2018 at 8:00 AM, Ina Panova wrote:
> +1 to keep RepositoryVersion.
>
> I also do not like the fact that it is quite long, that's why i do like
> the Snapshot, but thinking more of what snapshot is - is something that
> *you* need to trigger and it is not triggered automatically.
>
+1 to keep RepositoryVersion.
I also do not like the fact that it is quite long, that's why i do like the
Snapshot, but thinking more of what snapshot is - is something that *you*
need to trigger and it is not triggered automatically.
I'd say, we are working with repository versioning and not snap
I guess, you meant 'RepositoryVersions' there. Maybe it is just a typo,
or maybe your subconciousness already adepted to this change. ;)
I'm +1, because from the REST API or model view, you do not ask what
changed, but rather what is in that snapshot|version.
And since you are renaming all models
I’m not too worried about the change being too large. However, I agree with
@dalley though about snapshot not fitting my mental model of how I view
snapshots so any work seems like a loss to me.
I’m at -1 but am happy to talk more about it.
David
On Tue, Mar 20, 2018 at 11:08 AM, Daniel Alley
I think of a "snapshot" like a VM snapshot or a Windows restore point - an
archival copy of a very fluid and non-discrete system at one point in
time. By that understanding, the term RepositoryVersion probably fits
better.
I acknowledge the other benefits though. -/+0?
On Tue, Mar 20, 2018 at 1
The article you link to just says that "a snapshot is the state of a system
at a particular point in time". The point in time can be now or in the
past.
The current state of a repository's content would be described as the
latest or most recent snapshot of a repository.
I am not too worried about
I think the change would be positive in several ways. Snapshot is a more
familiar term that we can give content on what that means in Pulp (content
not settings). I think this will make Pulp more approachable. It also
aligns with the language aptly uses which I see as a good thing for clarity
in ou
I have some reservations about using the name Snapshot. Specifically, I
don’t think the snapshot term is a good fit. As wikipedia says [0], in CS a
snapshot represents a state of something "in the past.” How would we
describe the current state of the repository’s content then? I think
"current vers
"Snapshot" is a nice way to explain what a RepositoryVersion is, especially
in the context of Publications. "Publish a snapshot." I like the idea, and
I informally floated it around PulpCon but decided not to propose it
because:
- Snapshot is a little misleading about the actual data we store.
I propose that we rename the RepositoryVersion model in Pulp 3 to Snapshot.
The REST API would also change to use /api/v3/repositories//snapshot/
The Snapshot name is a better description of what a repository version is
and it is also much shorter in length.
Thoughts?
-Dennis
__
15 matches
Mail list logo
